- 0 Posts
- 5 Comments
Sometimes optimizing code comes at the cost of extra time and effort, and in those cases external factors like management and time constraints typically play a big role, but I often see projects bury themselves with pointless complexity that slows both development and execution down.
If developers didn’t have this stupid idea that they need to be typing to be productive, we could save a lot of pain. Sure you might quickly imagine a solution to a problem that e.g. uses a sorting algorithm, and you can pull a perfectly fine sorting algorithm out your ass in a minute, but what if sorting is completely unnecessary?
Questions like “can I remove the need for sorting” are never asked, and instead we waste time answering questions like “what is the fastest sorting algorithm”.
Sometimes spending an entire day staring into the screen without writing any code is exactly what’s needed to save time and produce a better solution.
I’m a different person from who you were talking to before. I’m just trying to understand why you feel they aren’t supporting Linux.
Wait, so what is this supposed situation we’re currently in?
I’m struggling to understand your version of reality.
Filesystems are incredibly antiquated, and while I don’t agree with Kent’s attitude, it is very important in the long run that filesystems catch back up.
As it stands just about any enterprise system you can poke a stick at is rolling their own customised file storage system, with a traditional filesystem typically being a misshapen dead weight sitting somewhere in the middle of it - existing because it’s the only thing the kernel can integrate with.
It is pretty important that this trend reverses, and bcachefs was a big step in the right direction. Unfortunate that Kent is the way he is.