Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Node.js needs a virtual file system

blog.platformatic.dev

Post reply on HN
Print view View original

251–260 of 275 posts

Re: Node.js needs a virtual file system

#251

Post by exe34 »

epolanski wrote: post #242
int_19h wrote: post #201

Earlier quoted context omitted.

We'd have a lot less enshittification all around, I suspect.

Sure thing, your nurse ain't gonna clean your mom, in the restaurant the chef ain't gonna prepare a dish he doesn't like, your accountant ain't gonna file your taxes if you've given him data he doesn't like, etc. Your paid to do a job, you're either professional or you aren't.

So you don't do your job and submit a PR you didn't even read, and I'm supposed to waste my time that I have to the explain at my next performance review? I didn't sign up to read slop, thanks! If my boss wants me to spend 10x time time on this kind of shit, he has to pick something else that I no longer have to do. My time is not elastic. It can't expand to fit your slop.

Re: Node.js needs a virtual file system

#252

Post by benatkin »

sauercrowd wrote: post #250
benatkin wrote: post #155

Earlier quoted context omitted.

Embed is read-only at runtime. This proposed vfs module for Node.js is a full virtual file system.

true

It's cool that it fits into golang's readable file system interface so it can be used polymorphically. I don't know if golang has very complete interfaces for a read and write file system that could be used for a full vfs. If it does, that's nice, and a starting point for a similar vfs! I'm also not sure whether it should go into the standard library or not.

Re: Node.js needs a virtual file system

#254

Post by AgentNode »

indutny wrote: post #29

Taking the question of whether this would be a useful addition to Node.js core or aside, it must be noted that this 19k LoC PR was mostly generated by Claude Code and manually reviewed by the submitter which in my opinion is against the spirit of the project and directly violates the terms of Developer's Certificate of Origin set in the project's CONTRIBUTING.md

[flagged]

Re: Node.js needs a virtual file system

#257

Post by Dylan16807 »

lmm wrote: post #234
Dylan16807 wrote: post #233

Earlier quoted context omitted.

There's a difference between "no license, all rights reserved" and "no license, public domain". Up until recently, you could assume that not having a license meant the former. But treating the latter as the same would just be silly. As far as I'm concerned, public domain counts as "an appropriate open source license".

> As far as I'm concerned, public domain counts as "an appropriate open source license". For material whose author is known and has explicitly placed it in the public domain, sure. For code that fell off the back of a truck, not so much.

I'm of course assuming the legal status quo holds, where code properly generated by LLM is also explicitly public domain. No shadiness involved.

(There's always a risk of an LLM copying something verbatim by accident, but if the designers are doing their job that chance gets low enough to be acceptable. Human code has that risk too after all. (And for situations that aren't an accident, with the human intentionally using snippets to draw out training text, then if they submit that code in a patch it's just a human violating copyright with extra steps.))

Re: Node.js needs a virtual file system

#258

Post by ovflowd »

indutny wrote: post #29

Taking the question of whether this would be a useful addition to Node.js core or aside, it must be noted that this 19k LoC PR was mostly generated by Claude Code and manually reviewed by the submitter which in my opinion is against the spirit of the project and directly violates the terms of Developer's Certificate of Origin set in the project's CONTRIBUTING.md

Matteo wrote a pretty neat article that effective counters your claim https://adventures.nodeland.dev/archive/who-is-responsible-f...

Re: Node.js needs a virtual file system

#259

Post by mpyne »

TingPing wrote: post #208
mpyne wrote: post #198

Earlier quoted context omitted.

> Like, why on earth would I spent hours reviewing your PR that you/Claude took 5 minutes to write? If the PR does what it says it does, why does it actually matter if it took 2 weeks or 2 minutes to put together, given that it's the equivalent level of quality on review?

“It works” is the bare minimum. Software is maintained for decades and should have a higher bar of quality.

> given that it's the equivalent level of quality on review?

Re: Node.js needs a virtual file system

#260

Post by lmm »

Dylan16807 wrote: post #257
lmm wrote: post #234

Earlier quoted context omitted.

> As far as I'm concerned, public domain counts as "an appropriate open source license". For material whose author is known and has explicitly placed it in the public domain, sure. For code that fell off the back of a truck, not so much.

I'm of course assuming the legal status quo holds, where code properly generated by LLM is also explicitly public domain. No shadiness involved. (There's always a risk of an LLM copying something verbatim by accident, but if the designers are doing their job that chance gets low enough to be acceptable. Human code has that risk too after all. (And for situations that aren't an accident, with the human intentionally u…

> code properly generated by LLM is also explicitly public domain

Where? I hadn't heard of any such ruling.

Post reply on HN