3 ms·
> I don't think any of the current JS frameworks are as comprehensive as Rails To someone who is switching from the Node ecosystem to Django REST, this seems l
by arcturus17 6y ago
> I don't think any of the current JS frameworks are as comprehensive as Rails
To someone who is switching from the Node ecosystem to Django REST, this seems like an understatement.
I'd be happy to use server-side JS for certain microservices that needed its performance characteristics, or for prototyping in something like Firebase functions. But the mere thought of building a standard fully-featured web app in Node depresses me.
- rektide 6y agothe whole trend though is that the server side is mostly a very tiny crud layer & a little bit of business operations. yeah tools like django are amazing packages. node is shockingly hardly any more tamed than it was 5 years ago, still rag tag Express for the most part. with who knows what for the data layer. but it just doesn't matter. alas! the actual application has been heavily front end biased, & all the real investment g architecture needs to revolve around that front end. it'd be great to have better out of box omakase js experiences. projects like hapi & fastify tried. but there's just not enough effort spent on the back end for that many devs to really care. and plenty of folks are using api based systems or hosted backends, appsync or some hosted graphql, where they can care even less about the backends. why be comprehensive when you hardly matter?
- joelbluminator 6y ago> mostly a very tiny crud layer & a little bit of business operations. Even if you have a SPA, which isn't a given (yes, trends. I know. They come and go), the API, data migrations and background workers can easily be 50% of your code and effort.
- arcturus17 6y agoYea, I have switched to Django with the intent of continuing to develop primarily SPAs. Like I said in other comments I'd only build an API in Express if I needed its particular performance characteristics. I've checked other tools in the JS ecosystem that serve as "low-code" API layers, but upon close inspection they always seem to have some limitations on the business logic you can write, and some of them lock you in to products. No thanks. I'm finding Django REST gives me a sweet middle ground between dev speed backed by great abstraction "magic" and freedom to customize as the app grows.