No, they had the option of having a real conversation in private about what we could do to improve the overall situation.
Instead what I got was "It'd be a real shame if you're no longer around", and other equally dismissive behavior, and considering this was a situation in which a maintainer was pushing for something that would likely have led to security vulnerabilities and was being dismissive of criticism I didn't feel that was something we could let slide.
> No, they had the option of having a real conversation in private about what we could do to improve the overall situation.
Abusing others individually in public, but expecting a quiet word on the side about “the overall situation” when it comes to your own behavior. I hope you realize something from this.
I want superiority de-coupled from technical expertise in the minds of the people who have the latter.
Taking his personal struggles out of kernel development and onto Hacker News was the escalation – pointing out his hypocrisy is only trying to get people who agree with him to realize that they’re wrong.
`I want superiority de-coupled from technical expertise`
So you want to take the power to produce taken away from the producers and coalesce it into the hands of those who do not produce for the sole purpose of controlling those who do produce.
I've gotten into arguments that were even more heated with maintainers who introduced data corruption bugs into code I wrote in the core block layer, without CCing me, which then hit users I support, and then had to track down, and then had them put up ridiculous fights over getting the bugs fixed.
Context matters, and also, if we're going to have standards for professional conduct they do need to be about more than just language.
We shouldn't be punching down, but we shouldn't be insulating maintainers from criticism when they're being incompetent, either.
Don't get me wrong, OSS does not mean it will build in any random configuration on any distro. The source is there.
Maybe 7zip could do better, but still...
Since you are writing to the location where rip is pointing to, you need to rewind to the beginning of the page first. Otherwise the program will crash if you're unlucky and rip is currently exactly at the end of an executable mapping. Low chance, but still...
One use case I have faced more than once are stuck processes in legacy build systems. For example, generating docs takes ages. Just killing the generator process will fail the build because the parent will notice. And since the build system is buggy/old, restarting the build will start from zero.
To support a block based filesystem on top of MTD an advanced FTL (Flash Translation Layer) is needed. Sadly most algorithms for decent FTLs are patented.
SSD vendors try hard keeping their magic sauce there own.
In Linux we habe some trivial FTLs implemented, but even these are toxic.
I suspect that while vendors would like you to believe it’s all patented secret sauce, I’m more skeptical. There’s too many vendors and they all perform roughly similarly with the controller chip speed and bus speed being more impactful. The FTL might be more impactful for disk longevity but I wouldn’t put much stock in consumer device numbers here. Even if Linux starts with an initially worse implementation, over time it should succeed because of cheaper costs multiplied by in aggregate a greater investment from stakeholders than any single private stakeholder could match. There’s a reason Apple and Amazon have written their own controllers and it’s largely because vendor solutions actually suck quite a bit when you start digging in.
I mean, technically, every Linux distribution is “just a(nother) live cd” with a slightly different configuration and some custom packages thrown in. To each their own, yeah?
