4 ms·
Looks cool! Do you have any examples or have experience with larger projects? For example, my React app has dozens of pages and some complex routing, and the b
by momothereal 6y ago
Looks cool!
Do you have any examples or have experience with larger projects? For example, my React app has dozens of pages and some complex routing, and the backend has 50+ endpoints and talks to different databases, RabbitMQ, etc.
When I see "shoe that fits all" solutions like this I'm honestly skeptical about the degree of freedom I get for more complex architecture needs. I've found frameworks like Next.js usually give you the freedom you need because it's basically pure JS.
Also, this seems like it has a good opportunity to automatically integrate e2e/integration testing.
- Martinsos 6y agoHey yes, we have been working on a React/Node app for two years some time ago, that grew to that size and some more. I understand the skepticism, to be honest I was also pretty skeptical when we started (I am still a little bit, a healthy dose :D!), but we think now we can get to the level of flexibility of serious web frameworks - it all comes down to figuring out where the flexibility is needed. Right now it is already pretty flexible - you can write any nodeJS logic and use any JS library, same goes for React components. What is tricky is hitting this right trade-off between flexibility and power, and we are thinking a lot about that. So to summarize, I agree, but am hopeful! e2e testing -> yes, that would be very cool :)! We don't have any testing capabilities yet, but will be looking into it. Regarding bigger projects - one thing I am excited about is the possibility to model not just one web app via the DSL, but to capture multiple services - for example multiple (micro)servers - and orchestrate them. I haven't explored that direction enough yet though, since it is not the priority right now.