interesthrow2

> The more I read about the js ecosystem, the more it seems the inmates are running the asylum

the issue is NPM. NPM is a bad package manager. A package manager that allows duplicates version of the same dependency is broken to begin with. People complain that fetching react-native results in hundreds of packages installed on their computers. How many freaking dupes? off course nobody is going to audit all that crap. Conflicts should be resolved upstream, which would lead to more stable packages to begin with.

NPM was developed by people who were clueless about package management and now are profiting directly from that shit-show, and even Node.js creator went on recording saying tying it to NPM was a mistake.

Just disrupt compliance with local construction regulations! it worked with illegal hotels before...

Not making Go routines values like Ada Tasks is what led to awkward solutions shouldered by the developer such as "context". Too many time Go developers were told to solve issues in user-land, this is the consequence of that.

> Why would a pedagogical project choose JavaScript of all languages?

I don't think the JS part is the issue. Node.js does I/O, files and co. The issue is that the article doesn't teach how to build a database at all.

It doesn't explain how to efficiently persist and fetch data from a file, indexing strategies with trees, concurrent file access,locking, basic transaction... that's what I expect from a tutorial about how to build a basic DB system.

> Fair warning: this is not for beginners. If you find the going too hard, start with a DB textbook.

which one can teach how to build a DB system from scratch? I'm not talking about SQL theory or implementing a SQL parser but the actual persistence, indexing part.

issues such as what?

Try to do that at Oracle or IBM. This is the culture fostered by Google executives, so they shouldn't be surprised if employees are publicly outspoken about their business decision. Is it a good or bad thing? If the higher ups are OK with employees publicly voicing their opinion then I don't see a problem. Management doesn't seem to be fighting this and Google does seem to work that way. The only issue I'd see is if a public petition was created and employee were coerced into signing it by their fellow workers under threat of being put "on the list".