3 ms·
I tried Sails about 3-4 years ago. Basically, you're taking the good from Rails (MVP code generation, relations, convention over configuration) and puts it on J
by everdev 9y ago
I tried Sails about 3-4 years ago. Basically, you're taking the good from Rails (MVP code generation, relations, convention over configuration) and puts it on JS, which unfortunately it's still a nightmare to develop CRUD apps with.
Async is great for lots of things, but not for your entire app.
If you want an async-first app, JS is probably a good choice. If you want CRUD, use Rails.
- mikermcneil 9y agomajor changes occurred here in 2017 with `await` making its way into the LTS release of Node - more on that: https://gist.github.com/mikermcneil/c1028d000cc0cc8bce995a2a82b29245 https://gist.github.com/mikermcneil/c1028d000cc0cc8bce995a2a...
- wild_preference 9y ago> Async is great for lots of things, but not for your entire app. That criticism is pretty dated now that JS has async/await. Given that you understand promises, async code has become trivial.
- everdev 9y agoIt's still an extra step to undo the async by default of JS. In other languages, the async is added only as needed, which I prefer.
- always_good 9y agoWhat do you mean by undo? Languages that aren't async by default (most of them) make async tedious when you do want it. A web application is precisely the sort of thing I want async. So it's in fact an extra step to write async code in most languages when building a web app. For example, just firing off a few requests (database, other APIs) in a route and awaiting them. JS makes this trivial.
- spraak 9y agoSails is definitely not a great framework, but overall it's not hard to do CRUD in Node.
- thorin 9y agoThat may be the case but coming from using frameworks such as .net webapi/mvc or spring do I really want to write all the controller/view code by hand every time when I don't need to or are you using other generators/methods for this?
- phillnom 9y agoJS is fine for CRUD