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

261–270 of 275 posts

Re: Node.js needs a virtual file system

#261

Post by Dylan16807 »

lmm wrote: post #260
Dylan16807 wrote: post #257

Earlier quoted context omitted.

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.

https://en.wikipedia.org/wiki/Artificial_intelligence_and_co...

This page has a pretty good overview.

> Both the federal and circuit courts in the District of Columbia have upheld the Copyright Office's refusal to register copyrights for works generated solely by machines, establishing that machine ownership would conflict with heritable property rights as establish by the Copyright Act of 1975.[16] As of March 2026, the Supreme Court of the United States has denied hearing challenges to the Copyright Office's decision.[17]

Re: Node.js needs a virtual file system

#262

Post by petercooper »

syrusakbary wrote: post #119
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

Fully disagree with this take. Not allowing AI assistance on PRs will likely decimate the project in the future, as it will not allow fast iteration speeds compared to other alternatives. Note aside, OpenJS executive director mentioned it's ok to use AI assistance on Node.js contributions: I checked with legal and the foundation is fine with the DCO on AI-assisted contributions. We’ll work on getting this documented.…

Not allowing AI assistance on PRs will likely decimate the project in the future,

I can't help but wonder if this matter could result in an io.js-like fork, splitting Node into two safe-but-slow-moving and AI-all-the-things worlds. It would be historically interesting as the GP poster was, I seem to recall, the initial creator of the io.js fork.

Re: Node.js needs a virtual file system

#263

Post by phendrenad2 »

habinero wrote: post #223
phendrenad2 wrote: post #98

Earlier quoted context omitted.

Why write open-source software at all, when the government could outlaw open-source entirely? What if an asteroid destroys Earth and there are no humans left to enjoy your work? At some point, you have to agree that a risk isn't worth worrying about. And your "worst possible outcome" is just the arbitrary outcome that you think has some subjective risk threshold. And it's certainly not one I agree with. Furthermore,…

> And it's certainly not one I agree with Well, it's a good thing you're not on the hook for defending against it, then. Like I said in another comment, you don't have a license just because they're cool and look neat. You have them specifically to guard against people like patent trolls, who are trying to wreck your shit and take your lunch money. It's not an abstract risk.

> Well, it's a good thing you're not on the hook for defending against it, then

If you are on the hook for defending against it, and your risk assessment is based on emotional, irrational fear and not an objective understanding of the risks, then you're doing people a disservice and should step down.

Re: Node.js needs a virtual file system

#264

Post by dakiol »

mpyne wrote: post #198
dakiol wrote: post #95

Earlier quoted context omitted.

Nobody wants to review AI-generated code (unless we are paid for doing so). Open source is fun, that's why people do it for free... adding AI to the mix is just insulting to some, and boring to others. Like, why on earth would I spent hours reviewing your PR that you/Claude took 5 minutes to write? I couldn't care less if it improves (best case scenario) my open source codebase, I simply don't enjoy the imbalance.

> 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?

One reason: if it takes 2 minutes to put together a PR, then you'll get an avalanche of contributions of which you have no time to review. Sure, I can put AI in fron to do the review, but then what's the point of my having an open source project?

Re: Node.js needs a virtual file system

#265

Post by girvo »

ThunderSizzle wrote: post #241
dirkc wrote: post #238

Earlier quoted context omitted.

Are your coworkers producing the code using LLMs? And what level of trust do you place in them?

For half my coworkers, their LLM code is better than their code.

That’s depressing. For 80% of my coworkers their LLM code is horrible. Only the seniors seem to use it well and not just spit out garbage

Re: Node.js needs a virtual file system

#266

Post by ThunderSizzle »

girvo wrote: post #265
ThunderSizzle wrote: post #241

Earlier quoted context omitted.

For half my coworkers, their LLM code is better than their code.

That’s depressing. For 80% of my coworkers their LLM code is horrible. Only the seniors seem to use it well and not just spit out garbage

I think that goes back to whether they are programmers vs engineers.

Engineers will focus on professionalism of the end product, even if they used AI to generate most of the product.

And I'm not going by "title", but by mindset. Most of my fellow engineers are not - they are just programmers - as in, they don't care about the non-coding part of the job at all.

Re: Node.js needs a virtual file system

#267

Post by dannyfritz07 »

ovflowd wrote: post #258
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...

Am I reading this right that Matteo is saying providence is not important because there are lots of historical cases of not having providence of code?

> Many contributions contain routine, non-copyrightable material, and developers still sign off on them.

> Compilers change code in ways developers do not always track. Template generators create output from their own logic. Stack Overflow answers are often copied into codebases without much thought about licensing.

Re: Node.js needs a virtual file system

#268

Post by mpyne »

dakiol wrote: post #264
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?

One reason: if it takes 2 minutes to put together a PR, then you'll get an avalanche of contributions of which you have no time to review. Sure, I can put AI in fron to do the review, but then what's the point of my having an open source project?

> but then what's the point of my having an open source project?

For some people, the point was precisely to improve the software available to the global commons through a thriving and active open source effort. "Too many people are giving me too many high-quality PRs to review" is hardly something to complain about, even if you have to just pick them randomly to fit them in the time you have without AI (or other committers) to help review.

If your idea of open source is just to share the code you wanted to work on and ignore contributions, you can do that too. SQLite does that, after all.

Re: Node.js needs a virtual file system

#269

Post by gonzalohm »

madeofpalk wrote: post #175
gonzalohm wrote: post #147

Earlier quoted context omitted.

Because sometimes programming is an art and we want people to do it as if it was something they cared about. I play chess and this is a bit like that. Why do I play against humans? Because I want to face another person like me and see what strategies they can come up with. Of course any chess bot is going to play better, but that's not the point

I don't think node virtual filesystems is anything like chess.

Solving problems is not like chess? I want to use my brain, not sure why that's so complicated to understand

Re: Node.js needs a virtual file system

#270

Post by dotancohen »

austin-cheney wrote: post #207
pocksuppet wrote: post #157

Earlier quoted context omitted.

Okay, what would your solution look like? from cities select state where name='Chicago' isn't really different from cities.filter(x=>x.name=='Chicago').map(x=>x.state)

Thinking small. In SQL databases a well put together database instance will typically have tables that with a single incrementing primary key column and some secondary key columns that point to unique records on other tables. That is the relational part of RDBMS. Its not about what it looks like. Arrays have fancy functional methods, but not object structures. Its more about whether it executes faster and comprises f…

That's a great idea - why not apply it to all JSON objects? In a way, we can already access a JSON array element by position. So all that is missing is a way to push a new element onto the array such that it:

- Assigns an immutable ID to the element, even if additional elements are added or removed.

- Returns that element ID when pushing.

Each "table" would be a top-level array item.

As for JOINs, I can think of a few syntax that are already supported, but none that I like. Any ideas?

Post reply on HN