Hacker News Reader

I don’t like the pattern of making frameworks less opinionated. I had hoped to use Blitz in the future but this pivot will undoubtably increase the complexity of the internals. Meaning more bugs. More hassle. Somewhere inside there is now a system to multiplex between different 3rd party frameworks. What they should have done is double down. Rails is one of the most popular and longest lasting modern frameworks for a reason.

View on HN

Blitz is not becoming less opinionated. It’s just the implementation that is changing.

The internals are significantly less complex now. Before, Blitz was a fork of Next.js, and dealing with that was a nightmare. Contributions dropped off significantly because of that.

Now features are nicely packaged and isolated. Much easier to reason about and contribute too.

Forking NextJS does sound like a huge hassle to maintain. Having a bunch of separated facade packages with some 1st party additional functionality is how I'd do it, too. But also allowing for multiple back-ends increases the breadth of the code base and in places where one package supports multiple back-ends you get increased complexity.

Reply on news.ycombinator.com