Read on Twitter
Framework/library churn.
I would like to be able to maintain my web app 3 years from now. https://twitter.com/joeemison/status/1287464411209310213
I would like to be able to maintain my web app 3 years from now. https://twitter.com/joeemison/status/1287464411209310213
I have worked on many ruby on rails apps that are still holding up really well 5-8 years later.
Cannot think of a single JS codebase that lasted more than 2 years without a signifcant rewrite.
Cannot think of a single JS codebase that lasted more than 2 years without a signifcant rewrite.
The event loop *sucks* in production too. Good luck trying to figure out where an error/exception is coming from.
Instrumentation/observability tools are very poor in JS land too. And no, logs are not the same observability.
No decent tooling for databases/ORMs. I’m talking real basic stuff that should just be obvious:
- prepared statements with MySQL
- a decent migrations tool
- decent detection of N+1 queries
- connection pooling that just works
- prepared statements with MySQL
- a decent migrations tool
- decent detection of N+1 queries
- connection pooling that just works
A good library (a la Sidekick) for background jobs with proper concurrency control that doesn’t poop out at non-trivial scale.
