3 ms·
I was thinking the same thing; so many of their original complaints have been addressed. However, one has not: unix still uses the NJ-style (vs the MIT style)
by GeorgeTirebiter 3y ago
I was thinking the same thing; so many of their original complaints have been addressed.
However, one has not: unix still uses the NJ-style (vs the MIT style), which is, if you can't figure out how to handle an error -- then don't. Also, put the burden on the programmer. Lovely stuff like that, which is core to the "unix philosophy".
- mwcremer 3y agoTo be fair, the web as a whole is like that these days, in that HTTP explicitly includes the user as part of the error handling (404, 500, 503). How many times have you hit "Reload" today?
- fanf2 3y agoThat was much less true by the end of the 1990s. Partly due to things like BSD’s improved signal handling. And partly due to the userland code quality improvements from the BSD and GNU rewrites. Shell scripting is still a nightmare for error handling, but by the end of the 1990s there were better scripting languages available to use when that matters.