logoalt Hacker News

austin-cheneyyesterday at 3:11 PM4 repliesview on HN

Most of the 4 justifications mentioned sound like mitigations of otherwise bad design decisions. JavaScript in the browser went down this path for the longest time where new standards were introduced only to solve for stupid people instead of actually introducing new capabilities that were otherwise unachievable.

I do see some original benefits to a VFS though, bad application decisions aside, but they are exceedingly minor.

As an aside I think JavaScript would benefit from an in-memory database. This would be more of language enhancement than a Node.js enhancement. Imagine the extended application capabilities of an object/array store native to the language that takes queries using JS logic to return one or more objects/records. No SQL language and no third party databases for stuff that you don't want to keep in offline storage on a disk.


Replies

dotancohenyesterday at 5:56 PM

  > I think JavaScript would benefit from an in-memory database.
That database would probably look a lot like a JSON object. What are you suggesting, that a global JSON object does not solve?
show 2 replies
iainmerrickyesterday at 5:09 PM

Why would you want a language enhancement for that, rather than just writing it in JS code? (or perhaps WASM)

Xenoamorphousyesterday at 8:21 PM

Like indexedDB but in Node?

dupedyesterday at 5:19 PM

> As an aside I think JavaScript would benefit from an in-memory database.

isn't that just global state, or do you mean you want that to be persistent?