4 ms·
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 a
by marianocordoba 8y ago
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/ https://aqueduct.io/
- LawZ 8y agoThank you for your comment. I tried aqueduct, but at the end, I felt node is the right choice (for now).
- graphicbeacon 8y agoHey 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 https://youtu.be/vvDomA-ru3E
- isoos 8y agoNot 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.
- marianocordoba 8y agoI mean, in my case i can share some utilities, but most of the code is just too specific to client/server.
- thosakwe 8y agoThere is also Angel: https://angel-dart.github.io 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)
- marianocordoba 8y agoThanks for sharing and great job btw! I will give it a try soon.