4 ms·

I'm the biggest JS-on-the-server sceptic of them all, given my past experiences. But this was pre-typescript. If a TypeScript ORM with automatic schema migrati

I'm the biggest JS-on-the-server sceptic of them all, given my past experiences. But this was pre-typescript. If a TypeScript ORM with automatic schema migrations and decent expressiveness comes around, I'd be willing to give NodeJS another shot. But so far, nothing comes even close to the productivity of Django + ORM + Django Rest Framework. For your typical CRUD app, this will walk circles around any current JS solution. Even if the lack of static typing eventually becomes a bit of a pain.

jcrben 10y ago
Have you seen typeorm? https://github.com/typeorm/typeorm https://github.com/typeorm/typeorm
- silviogutierrez 10y ago
  I have. It's a great improvement over other ORMs in the NodeJS space but pales in comparison to Django's ORM. At least for now. Relationships must be done manually, including joins, traversing, and many to many. Sometimes doing: w = Widget.objects.get(pk=2) w.category.author.name Is just all you need. And Django makes that trivial.
Daishiman 10y ago
I'm on the same boat. Django or Rails are so much more productive for me that I feel that most of the Node.JS love for this sort of domain comes from people who have never tried anything better.
- throwanem 10y ago
  The operative words here being "for me".
sametmax 10y ago
This. Yes the site won't be as fast, and yes you don't have realtime. But if you need a regular web site, not a real time app with 100000 users, then nothing BEAT those techs. They are mature, stable, productive, and incredibly flexible. If you use anything else and you need something that is not "the typical hello world", you will have to write it by hand. With DRF ? You google it, you find a module and call it a day.
douche 10y ago
It sounds like you are describing C# with Entity Framework. Throw in the self-hosted OWIN webserver and WebApi or Nancy and you're good to go. I'm not really up on the state of DotNet Core or whatever they are calling it this week, but when that is shaken out, I'll be interested so see what kind of inroads it makes on Java and Python in the Unixy server world.

jcrben 10y ago

Have you seen typeorm? https://github.com/typeorm/typeorm https://github.com/typeorm/typeorm

silviogutierrez 10y ago
I have. It's a great improvement over other ORMs in the NodeJS space but pales in comparison to Django's ORM. At least for now. Relationships must be done manually, including joins, traversing, and many to many. Sometimes doing: w = Widget.objects.get(pk=2) w.category.author.name Is just all you need. And Django makes that trivial.

Daishiman 10y ago

I'm on the same boat. Django or Rails are so much more productive for me that I feel that most of the Node.JS love for this sort of domain comes from people who have never tried anything better.

throwanem 10y ago
The operative words here being "for me".

sametmax 10y ago

This. Yes the site won't be as fast, and yes you don't have realtime. But if you need a regular web site, not a real time app with 100000 users, then nothing BEAT those techs. They are mature, stable, productive, and incredibly flexible. If you use anything else and you need something that is not "the typical hello world", you will have to write it by hand. With DRF ? You google it, you find a module and call it a day.

douche 10y ago

It sounds like you are describing C# with Entity Framework. Throw in the self-hosted OWIN webserver and WebApi or Nancy and you're good to go. I'm not really up on the state of DotNet Core or whatever they are calling it this week, but when that is shaken out, I'll be interested so see what kind of inroads it makes on Java and Python in the Unixy server world.