Given that most of this code was originally targeting systems from the 1960's and 70's, I can't imagine there being an insurmountable number of lines of code
According to Wikipedia, Gartner estimated about 200 billion lines of COBOL code in 1997. To put that in perspective, that's more than the total amount of open source C code tracked by OpenHub.net. Can you imagine persuading someone to rewrite all of that C code in a newer language?
why wouldn't we include her full name?
Because mentioning a woman in IT triggers far too many snowflakes who will moan about how it's manly men's work to sit inside an office and type on a keyboard - no place for women at all.
implementing a minimum-wage increase throws some of the poorest of poor out into the unemployment line to starve
Bullshit. That's like those old arguments about workers compensation or an ability to sue for damages encourages workers to permanently disable themselves. You've been infected by poisonous political rhetoric that was old and worn out more than a century ago.
Which results in weird startup issues occasionally. I managed to hang my laptop trying to add an autostarting emacs server to my user session. Which shouldn't influence system boot, IMO, but it did
That's the kind of scope creep I was referring to elsewhere which IMHO is yet another sign that Lennart just doesn't "get" the idea of a *nix system or multiuser systems in general, but maybe I'm reading too much into it and his blog posts.
Morality is irrelevant; minimum wage is an efficiency model.
The efficiency model is to exploit the weak and desperate as much as possible so it is indeed a moral issue to draw a line beyond where exploitation cannot go.
I really don't know why you wrote so much to build a house of cards upon your faulty premise. What exactly were you trying to do with all of that? What's with the weird attack at the end?
Ever studied dynamic systems? The journey from Newton's first principles to the Hamiltonians and Lagrangians too a couple hundred years for a reason: the math of modeling the evolution of a stateful classical system is very distant from the math that describes that system in some elegant way. The connection between the two is non-obvious, to say the least.
State in programming is very straightforward, though I guess it's equally distant from the elegant mathematical systems of the lambda calculus and combinator logic.
Not to mention the fact that the best programming is only frugally stateful anyway.
That's certainly the current fad. The best programming is "whatever approach keeps things simple", which is never going to be the same tool for all jobs.
"In the face of entropy and nothingness, you kind of have to pretend it's not there if you want to keep writing good code." -- Karl Lehenbauer