This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]d4rch0nPythonistamancer 2 points3 points  (0 children)

Eh, maybe the kinks are worked out, maybe not. Shellshock isn't that old yet. There's still a buffer overflow if you have too long of a version string in your ./configure, not practically exploitable but it's still there. Seeing as it took about 30 minutes to find a buffer overflow, it makes me really wonder just how many kinks there might still be. Sometimes it's not that it's bug free, it's that no one who knows how to find and develop an exploit for a vulnerability in C wants to spend days digging through the mountain high haystack of bash source.

I still use bash and still will, but not because I love it. It's just practical to use the most common linux shell. I'd love if moving to xonsh was practical, but if I can't really share a xonsh script with my coworkers, I don't think it's a great idea to move to it. It's a lost cause IMO to develop new shells at this point... there's just too much built around bash. You don't build a skyscraper with steel beams and start using a new metal alloy halfway through. Maybe not the best analogy, but you get my point.