[jamal-kumar]

The first thing I look for when starting a new project is if I can't be served by the standard library in whatever lang I'm using, to find dependencies that don't also depend on a bunch of code that I will have to indirectly depend on. The code I wrote like that still runs like ten years later without much problems having to update it. The code I worked on which depended on whatever flavor of the year framework people were hyped on for no good reason is rotting.

[dahfizz]

Absolutely. This is where the real dependency bloat in ecosystems like npm come up. You may only include a handful of reasonable dependencies, but each of those have dozens of their own dependencies, and so on and so on.

[tapanjk]

This is true for [probably all] frameworks? If I develop a microservice using Spring Boot, dependencies are inevitable.

However, I think the blog post reflects a strong desire of many developers (I am one of them.) Achieving this vision, at least in commercial software, can be a utopian dream.

[jamal-kumar]

I'm super allergic to the nodejs ecosystem, it's so bad.

I also get away in my professional life using it for pretty much nothing and it's great. There's a reason Ryan Dahl moved on to Deno.

People who think it's somehow necessary or integral to getting a website going are deluded hypebeasts.