4 ms·
The article assumes that "best practice" in 80s was the same as it is today. It was not. Best practice evolves.
by rumcajz 12y ago
The article assumes that "best practice" in 80s was the same as it is today. It was not. Best practice evolves.
- lelf 12y agoNot to mention that it is fscking portable and no, it's not easy at all to use all the shiny new features on that IBM whatever that it perfectly runs on.
- DougWebb 12y agoBest Practice evolves because of lessons learned about the problems in previous practice. I think the point of the article isn't that Bash wasn't originally written with 2014 Best Practices, but that it hasn't been kept up to date and therefore hasn't been improved based on those lessons learned.
- Pxtl 12y agoI think tons of globals smeared across several files was bad practice back in the 80s.
- rumcajz 12y agoIIRC they were not considered to be the pinnacle of good style, but they were much more acceptable than they are today. Interesting fact: In early 60s there was a serious discussion about whether stack frames (called activation records back then) should be global or not.