Hacker News Reader

Comment by everdev | Hacker News Reader

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.

View on HN

major changes occurred here in 2017 with `await` making its way into the LTS release of Node - more on that: https://gist.github.com/mikermcneil/c1028d000cc0cc8bce995a2a...

> 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.

It'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.

What 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.

Sails is definitely not a great framework, but overall it's not hard to do CRUD in Node.

That 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?

JS is fine for CRUD

Reply on news.ycombinator.com