3 ms·
There is no framework. Just simple JS calls and bindings to HTML with somebody defining REST or GraphQL backend. And some eye candy CSS. The point is that with
by bitL 3y ago
There is no framework. Just simple JS calls and bindings to HTML with somebody defining REST or GraphQL backend. And some eye candy CSS. The point is that with ES7+ JS can be finally readable and not a spaghetti code monster so anyone can easily understand and extend any code.
- pwb25 3y agogood luck with that
- duxup 3y agoIt really sounds like you don’t have any need for a framework and so of course it doesn’t seem like you need it.
- bitL 3y agoI was involved with some deep React apps that utilized all kinds of advanced patterns and I simply don't see the need for most apps I see around. React is neat if you have thousands of concurrent updates coming in all the time where dependency graph is a killer. But only a few companies need it - why then force this on all frontend devs by default? It's like with big data - let's push everything to Hadoop/Spark when our SQL database fits into 20MB etc.
- duxup 3y agoThere are a lot of sites that use react that don’t need it. Some uses benefit from a good framework.