My experience having written all of the above is that JS is significantly more fragmented, and also has to deal with a frontend-backend severed line. Rails, Flask, Django (and PHP, purely server side JS that generate HTML with templates like express) are basically all "backend serving frontend and templating". Front end JS is more of a "frontend + backend with frontend serving backend" in the form of server side rendering being more akin to running a browser, loading the frontend, and then serialising that to a page. This is the complete opposite of the above. It's kind of a different mindset,
I think it's simply that (and this is from my memory only): Node.js was THE first back-end JS thing, and its "micro" philosophy kind of set the precedent for everything else that follow in that space. It was the time when people started to feel Django/Rails are cumbersome for some of their needs, too, so the MVC approach never caught on for JS devs. So I think it's just popularity. Pick whatever tool you deem suitable!
At the start of node.js, I frequently saw full web applications written in it "traditionally", fetching data and writing it into pug/haml/jade/handlebars/whatever else templates (during the callback-pyramid-hell days). It was pretty much just another stack like a less opinionated django. People used express, returned HTML, etc. Then the SPA frameworks came into the fray, and I never really saw node.js being used server side like that much anymore.
社区原声 · 热门评论
打开原帖核对