ithrow

Nodejs devs seem to be doing fine? and I would say their development is faster than most devs working on other stacks. Nodejs is also a top 3 server stack and growing.

For free online textbooks these ones seem to have good reputation on the Internet. I did the 'pre-algebra' and 'algebra and trigonometry' books, found them good. Do all the excersices (very important), sometimes I got stuck (every books misses edge cases) so be prepared to look at other resources.

sqlite is accessed via a socket? defeats the whole purpose of using sqlite.

Many here are mentioning using one sqlite file per customer but that sounds like a nightmare for migrations and analytics.

SQLite is great and all these new services and articles are nice but intentionally shadowing lots of complexity.

Access to monstrous machines is easy today and you have very fast runtimes like Go and the JVM that can leverage this hardware.

You really think AWS is going to be offering Clojure SDKs?

Remains to be seem for Kotlin but the others haven't grow enough to develop a big ecosystem of their own.

Because it's a more 'get shit done' language (with a fast solid runtime, good stdlib and and fast compiles), it's not concerned with giving its users the means and ergonomics to produce the most beautiful programs, instead, a language for the majority of backend developers.

That's the whole point, make the country poor.

Valid point anyway

Pros of Playwright/Puppeteer:

Reuse existing HTML/CSS knowledge

Cons: Requires an external service or shelling out to an external process

Pros of using a pdf lib:

Probably better performance, simpler architecture by being in-process.

Cons: Ad-hoc language for designing the PDF.