Re:Dart vs. node for flutter app server side
by marianocordoba on Saturday March 02, 2019 @01:37PM
(#19290450)
I had the same question and ended up with Node, just because there are a lot of resources and a big community to help. Also, I can't share code between server and app, so I can't save code by using Dart on the server.
But in the end both can be used and is your choice, none is better.
If you go with Dart, I recommend you to check out https://aqueduct.io/
[ Parent
| on HN ]
Re:Dart vs. node for flutter app server side
by thosakwe on Monday March 04, 2019 @01:38AM
(#19299257)
There is also Angel: https://angel-dart.github.io
People tend to ignore it in these conversations (which frankly, is often disheartening), but it’s been used in production, and is nearly done with a large upgrade.
(disclaimer: I am the creator)
Re:Dart vs. node for flutter app server side
by marianocordoba on Sunday March 10, 2019 @06:46AM
(#19351382)
Thanks for sharing and great job btw! I will give it a try soon.
Not sure why you say you can't share code between server and app: if the code is in a common library that both import, it can be shared.
Re:Dart vs. node for flutter app server side
by marianocordoba on Sunday March 10, 2019 @06:45AM
(#19351380)
I mean, in my case i can share some utilities, but most of the code is just too specific to client/server.
Re:Dart vs. node for flutter app server side
by LawZ on Saturday March 02, 2019 @02:24PM
(#19290679)
Thank you for your comment.
I tried aqueduct, but at the end, I felt node is the right choice (for now).
Re:Dart vs. node for flutter app server side
by graphicbeacon on Sunday March 03, 2019 @04:33AM
(#19293610)
Hey LawZ, thanks for sharing your resolve. Perhaps you could shed a bit more light on your decision.
Also, would it not be better to save yourself the context-switching between ecosystems and sticking with Dart?
I made a YouTube video series on Aqueduct and would love to gather your thoughts: https://youtu.be/vvDomA-ru3E