hey I wasn't aware of this project - definitely looks interesting with significant number of features+plugins.
In my case I wanted something fairly simple which I can setup on a personal server/NAS, and which I can use to fill new spendings per category with a browser, and visualize variations per category over time.
I agree, but from my observation bad code is more significantly more widespread in Node. The tooling is just incomplete by default, you have to setup yourself. Further the projects structure is completely different on every project (and typically not nicely done).
I believe for small projects it can be interesting, you can have an instance up using 50 MB ram. Also the language is widely used. JS is used in the frontend so they believe it's great for the backend also because you "reuse" the code. In my experience close no code is reused from frontend to the backend and vice versa.
Definitely agree with this. I have been switching from developing in ruby into Node 2 years ago as I thought this was "the new thing" for web apps. Now I just want to move away from Node. Large scale Node applications looks like 20 years ago, copy and paste all over the place, cheap libraries, no developer happiness, you have to reinvent the wheels, etc.
I used rails about 3 years with multiple versions, and recently started to work on Node.js. Typically pure express-based websites tend to become quite messy, at least the projects I worked on. Started a new site with Sails.js 1.0 (beta) recently. It's definitely not as solid as rails. But overall I am pleased so far, except some shortcoming, ex. the lack of out-of-the-box migration system.