How is slate-ntfs different from NTFS-3g and the NTFS 3.1 kernel implementation?
-First of all, slate has a fuller VFS implementation, allowing Steam to see drivers natively. This means that Steam can see drivers directly, without direct intervention.
-User API: comes with an API to easily get driver manufacturer. Has Python, C and Rust support.
-Rust driver, C adapter: can be used with kernels as old as 5.15 while preserving memory safety.
-This code also runs on ARM64 (not fully tested)!
Manual code isn’t magically bug-free. Judge the project by its quality, not whether AI helped write it.
I never said manual code is bug-free. But all errors in manual code are human-made.
I judge a project based on the apparent judgement of it’s owners/maintainers.
A large part of software engineering is using your judgement, whether it comes to overarching design, language choice, algorithmic implementations, but also chosing dependencies, tool, collaborators and documentation. Humans make mistakes, but can learn from them and improve over time. So while a mistake can be embarrassing andor costly, in the long term they are part of the learning process.
When you opt for using LLMs for any of that you are outsourcing your judgement to a box that’s incapable of reasoning or learning. You will still get bugs and mistakes will be made but noone except Scam Altman and Wario Amodei will be happier for it.
Studies also indicate that this is actually negatively impacting our cognitive function in the long term.
And then we can add the ethical and environmental concerns on top of that, and suddenly the collective judgement of a project accepting or condoning LLM use is looking pretty damn bad if you ask me. Even before reading a single line of code in the repository.