back

by sergiotapia·1y ago·view on hn ↗
That's javascript ecosystem in general. A revolving door of breaking changes and yet another web framework. Not to mention many many many tiny libraries.

To give you a simple example.

"What's the best web framework these days for fullstack JS work?"

Ok, Hono, found that. Installed it, great, it even runs well with Bun. Holy shit, it seems like JS is catching up! But now how do I talk to my database? Hono has no such thing, you're on your own.

Ok, let's use Prisma but setting that up there is no one-true-way, it's all blog posts and praying you followed the right one. Also Prisma seems to now work with joins?

Migrations? You set that up manually.

Deploying is another story.

Very painful.

---

Compare to Laravel, Rails or Phoenix. All these things baked in, one blessed paved road to tackle the common things 99.9% of web apps need. We are blessed to have all this great work for free, right at our fingertips. People donated a lot of time and love into building them. I hope javascript one day reaches that level.

It's still cowboyitis out there.

2 comments
I've never heard of any of these tools. Maybe you should be more critical of the answers you get?

I've been sitting here as a react developer, quite stagnent in my toolset, using the same React I've been writing since 2015. The 'newest' technology I picked up was Typescript back in 2019.

> Ok, Hono, found that.

Weird that you went with some framework I've never heard of, and that definitely does not come up when I google for best fullstack JS framework.

> Ok, let's use Prisma but setting that up there is no one-true-way

Maybe the docs? https://www.prisma.io/docs/getting-started

> Deploying is another story.

I mean deployment always brings some complexity, but for the majority of JS frameworks you can get started by building it, throwing it in a docker container, and hosting that somewhere. I don't see what's difficult about that