They have wasted so much time talking shiz about a system they did not want to understand
You write “engineers with decades of skill pointing out obvious and blatant fundamental problems with the design and scope that first-year comp sci students would be corrected for” weird. It may require experience to spot the difference, though.
Churn != Improvement
Yes. Just today. And every day of the last 26 years. GMail delivery is no big deal. but outlook freaks out in ways I just don’t care to solve.
Smbfs by autofs for decades. 0 issues.
setup
‘set up’, my dude. Two words, as a verb.
Neither. Both have fundamental issues toward confident updates and validation of software, speaking as someone who used to run the security response for an Enterprise OS vendor.
I’m looking at CloudStack now, and it’s got some promise despite one odd glitch. I may try to stick with it .
Every time I see flatpaks, the former OS security dev in me cringes.
JHTerpstra taught me so much in the 00s, and his lessons haven’t stopped being relevant.
Redhat 35 years ago
… Was 3 years before it was created.
30, right?
Started with slackware, moved to RHL, worked on OL while suffering SuSE for UL and moved to RHEL.
The only intersect between me and 33 years of Linux is the darkest times groveling through the over-engineered frailty of SuSE while working on UL.
None of the rest even have a mention here
Nice chart?.~
I only do BSD, now.
I used to do GPL, and I still support free software and everyone’s ability to modify and extend projects for new and better purposes.
When some South Koreans were jailed for upholding my license terms when they spotted their employer violating them, and the FSF did little and less to help them avoid jail - which happens sometimes in Korea - I knew the GPL was still a good idea but in practice it exposes people to risk.
I can’t have that happen for my software again.
Useless with getting news out, useless in preventing a dictator from taking control.
American militias as mentioned in the second amendment are really no actual use, are they?
no fallbacks is bad practice.
This is how you know they’re extra lazy – no “please enable javascript because we suck and have no noscript version”.
“nah bruh this site is considered broken for the mere fact that it uses JavaScript at all”
A little paraphrased, but that’s the gist.
Isn’t there an article just today that talks about CSS doing most of the heavy-lifting java is usually crutched to do?
I did webdev before the framework blight. It was manual php, it was ASP, it was soul-crushing. That’s the basis for my claim that javascript lamers are just lazy, and supply-chain splots waiting to manifest.
Same. This is the way.
Containers carry concerns around validation of container contents and, by extension, host contents. This has been well-discussed and is beyond the scope here.
But I do hope for an installation free of container mess.
Two groups of people went to war over a difference of opinion.
- New! Different! Change! Bad!
‘Change resistance’ was the standard gaslighting. No one said ‘different bad’, in a time when enterprise linux had just switched from sysVinit to upStart. What they said was “this is built bad and wants to do too much, poorly. We don’t like this.”
And the response was “you’re old, you hate change,” and similar fallacies.
- Hey, this works better than the old way. Let’s use this instead.
I think you mean “I don’t know how to do this in the normal way, so I’ll try this other thing.”
systemd does a LOT of things
… incompletely …
that used to be individual jobs handled by separate things.
does everything and breaks unix philosophy, rather than a suite of tools that adhere to it
…for ‘itself’ versions of ‘it’.
Yeah, I interviewed for a job that required a lot of Systemd work. I crushed the practicum super hard and my genius new boss teached numa pessimization for DB load (bit if a click bait start but she hashed it out perfectly and it will come up again) before I declined on rates.
It’s not that it’s hard work. It’s that Systemd is a bad tool; and we deserve the day of crying wreckage it will gleefully cause one day.