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)!

all 25 comments

sorted by: hot top controversial new old
[–] [S] 14 points 1 month ago (3 children)

My condolences to anyone still stuck with ntfs partitions

  • source
  • hideshow 3 child comments
  • [–] 2 points 1 month ago (2 children)

    I still do some sneakernet file sharing with a Windows user where BitLocker support would be nice (we currently use VeraCrypt).

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 1 month ago (15 children)

    You think NTFS isnt fucky enough without putting slop in the driver?

  • source
  • hideshow 15 child comments
  • [–] [S] -1 points 1 month ago (14 children)

    A lot of your Lemmy comments seem to be just calling everything slop...

  • source
  • parent
  • hideshow 14 child comments
  • [–] 1 point 1 month ago (11 children)

    Yeah, well there's alot of slop being pushed around here. Do you feel I've been wrong so far?

  • source
  • parent
  • hideshow 11 child comments
  • [–] [S] -2 points 1 month ago (10 children)

    From what i can see, you just seem to jump into all these repos, check if Claude is listed in the repo but, don't actually check the code.

    AI is also used for things like code review and documentation. Also, if the feature set is good and the code properly reviewed, its not a bad thing imho. Even the Linux Kernel devs will use AI these days..

  • source
  • parent
  • hideshow 10 child comments
  • [–] 2 points 1 month ago (9 children)

    Well first of all, if you look at some of my comments you will see that I usually look closer than that. But its true that my opinion of a project plummets as soon as I see a single LLM artifact. I don't agree that there has to be a certain amount of low quality commits for the project to be slop. Its more like if someone pissed in the coffee. The problem isn't the actual volume of urine, it's that someone pissed in it in the first place.

    Second, I reject the notion that I have to prove that any code is worse for having LLM extrusions in it. The evidence is clear, you need to be overwhelmingly proficient in any field to be able to catch the multitude of errors that the stochastic parrots shits out and you need to be constantly in your guard, because the LLM is trained to give you output that looks good, not good output.

    And if one is even slightly impressed over the quality of what the LLMs output it's a confession that the person don't know enough what he/she just prompted to tell the difference.

    Third, even if the output was pristine, objectively correct, and for every given purpose relevant and optimized, just the glaring ethical and environmental concerns should be enough for any decent human to stay the fuck away from the models that are typically used for coding, review and translation. Or are you going to tell me that all the projects I have commented on use ethically sourced open weighted models that run on green energy? Yes this too determines if it's slop, because it's slopping society too.

    Also, I am sorry, but "even the Linux kernel devs" is a ridiculous justification. They have as a collective done some amazingly stupid shit over the years and Linus is included in that even before bringing in LLMs in the development.

  • source
  • parent
  • hideshow 9 child comments
  • [–] [S] -4 points 1 month ago* (last edited 1 month ago) (8 children)
    1. The dev has commits in C (which, I should probably tell you is a difficult programming language), stretching back to 2023.. Pre "AI". So, I'd argue, they definitely have some real knowledge of development.
    2. Even if we ignore this project, this dev has more evidence that they can write code than you (unless they were using Claude in 2023).
    3. Any developer will tell you how long it takes to find things in a code review. When I run manual code reviews, my computer isn't powered by unicorn farts for the next few hours.
    4. Are you seriously arguing that you're more knowledgeable than the kernel devs here? lol. They're not perfect, but Linus's job is LITERALLY code review. I'd argue he knows about the quality of AI code more than anyone else
    5. Have you got any repos you want to brag about that you developed yourself? I'm sure they're super complicated projects

    I'm not arguing its ethical.. I would argue that bullying developers isn't ethical though.

    As a part of the OSS community, I'd openly welcome for you to start a AI company that uses Green power and only open source models for training (yes, thats all possible). That would solve the problem wouldn't it? But, I guess you'd probably need to be a technical person to do that..

  • source
  • parent
  • hideshow 8 child comments
  • [–] 0 points 1 month ago (7 children)
    1. I too have lots of experience in C and I fucking suck at it.

    2. You seem awfully confident given that you have seen exactly zero lines of my code?

    3. if you are implying that your computer draws as much power when you manually code review as an LLM does you are either full of shit or doing something amazingly wrong.

    4. I better fucking hope that there is noone on that team that is worse than me at kernel development, but that does not mean that some of them are not absolute dumbfucks. Nice strawman tho.

    5. Not really, most of my code is closed source and all of it is shit tier. It's completely LLM-free however

    If you believe my comments constitute bullying you have lived a sheltered life my friend.

    "Make a company that solves these problems then!"

    ... dude. Are you all right?

  • source
  • parent
  • hideshow 7 child comments
  • [–] 1 point 1 month ago (1 child)

    Manual code isn’t magically bug-free. Judge the project by its quality, not whether AI helped write it.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 month ago

    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.

  • source
  • parent
  • [–] [S] 0 points 1 month ago (4 children)
    1. What's your point?
    2. So you haven't checked their C code either? The bar for bullying is pretty low
    3. If your code reviews only take a few minutes, you're not really looking for bugs.. Or your code is very short, or an extremely high level language. When I say code review, it also basically runs full unit / blackbox tests on everything and check it matches contents. Doing that is not normally a fast job.
    4. Again, Linus uses AI and specifically allows it in kernel.. His job these days is code review.
    5. Well, sounds like their code might be better than yours..

    Why not actually explain whats wrong with the persons code..

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 1 month ago (3 children)
    1. I dont know, you brought it up?
    2. Maybe I have?
    3. Code review is code review. Tests are tests, don't conflate the two.
    4. Yes he does, that's a mistake and I think the old Linus would scream profanity at you for idolizing him like that.
    5. Dude, I don't know if your reading comprehension is lacking but I've never said I code well. I suck, I know it, I own it and don't have to rely on clankers to fuck my code up

    And why would I waste my time reviewing a strangers slop? They did not care while writing it, why would I care to read it?

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] 0 points 1 month ago (2 children)

    You care enough to check the repos of each post to identify if they're claude to bully them evidently.

    Not great for the linux community..

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 month ago (1 child)

    I think it's fair to point out slop so that those who care can avoid the projects. If you still think this is bullying, well too bad I guess.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 0 points 1 month ago*

    That's not what you're doing.

    What you're doing is just going to the project page to check if you can call it slop (and bully devs) based only on the maintainers listed (without doing any actual work).

    I'd argue thats no better than vibe coding by people not interested in learning. Both sides aren't interested in doing any real work, but scoring some lazy wins..

  • source
  • parent
  • [–] 4 points 1 month ago

    It was made in 4 days and has claude as a contrinutor its just slop.

  • source
  • [–] 1 point 1 month ago (3 children)
  • [–] [S] 1 point 1 month ago* (2 children)

    I don't think the author is saying "YESSS.. Use NTFS". Some people are stuck with NTFS partitions though, because they need to share with windows Machines or other reasons.

    And if you are, its not a bad thing to have better options.

    Would I format my second NVME to NTFS and use this? Nope.. But, if you're stuck with NTFS (or just not fully committed to Linux), transition technologies like this can help.

    I look forward to the day that the last NTFS, APFS , FAT and HFS+ partitions on the planet are permanently deleted and replaced by better options. But, until that time...

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 month ago (1 child)

    I'm not asking why one would use NTFS.

    I'm asking why there's yet another NTFS driver when there are plenty out there, with the ntfs3g proven robust.

    The only way folks have been trying to implement it better is with native kernel code to replace the current buggy one.

    I'm asking why anyone would use this thing instead of the ones I mentioned above, and don't say "because it's in Rust".

  • source
  • parent
  • hideshow 1 child comment