News for hackers. Stuff that matters.
Re:Building a faster, smarter, Chromebook experience with th... by lmm on Thursday June 13, 2024 @06:49PM (#40675733)
Perhaps. In my experience a bad driver is better than no driver; not wanting bad code in your codebase is reasonable, but gets less reasonable when you also refuse to offer an API. And even if your code does meet their quality requirements, it can still get rejected for kernel-politics reasons.
Re:Building a faster, smarter, Chromebook experience with th... by account42 on Friday June 14, 2024 @03:48AM (#40678569)
Unless you are going to provide examples then I am going to assume that " kernel-politics" refers to things like rejecting "drivers" that can only used with a closed source userspace blob. In those cases the reasons have technical merit - how are the kernel developers supposed to maintain an effectively proprietary API without any idea how it is being used.
Re:Building a faster, smarter, Chromebook experience with th... by lmm on Sunday June 16, 2024 @06:05PM (#40700509)
No, I'm talking about cases of not liking the way of doing things, e.g. how we ended up with CFS which was a watered-down reimplementation. (ReiserFSv4 is another example of code that met the technical bar and was rejected for purely non-technical reasons, as much as few would disagree with that).