The suggestion here seems to be try even more abstractions within the React ecosystem, but in my experience simplicity, stability, and an improved developer experience only came after abandoning React and turning to standards-like solutions (e.g. Vue, Riot, Custom Elements, plain HTML and CSS).
We should strive for simplicity and we can achieve it in many different ways. There is no one size fits all solution.
The thing is that Blitz boils down common problems into simple patterns and it is an interesting offer if you need them to be solved so you can focus on the end product more. DX is great when everything follows one general pattern which is React in this case.
Sounds like a monolithic web framework architecture of the past, which is no surprise because React prefers to operate in its own framework-like ecosystem.
I’ve found that independent libs with clean, interoperable API surfaces composed in any way you need is a better approach.
The suggestion here seems to be try even more abstractions within the React ecosystem, but in my experience simplicity, stability, and an improved developer experience only came after abandoning React and turning to standards-like solutions (e.g. Vue, Riot, Custom Elements, plain HTML and CSS).
We should strive for simplicity and we can achieve it in many different ways. There is no one size fits all solution.
The thing is that Blitz boils down common problems into simple patterns and it is an interesting offer if you need them to be solved so you can focus on the end product more. DX is great when everything follows one general pattern which is React in this case.
Sounds like a monolithic web framework architecture of the past, which is no surprise because React prefers to operate in its own framework-like ecosystem.
I’ve found that independent libs with clean, interoperable API surfaces composed in any way you need is a better approach.
And does Blitz really look like this:
Blitz
Next
React
Express
Node