ssh, bash, vim and .csv, on top of UNIX.
Ask HN: What frameworks are currently used in a modern web stack?
121–125 of 125 posts
Re: Ask HN: What frameworks are currently used in a modern web stack?
#122Earlier quoted context omitted.
I'm saying this as a Node.js user myself so I'm not putting down Node but... Node.js is not a "Framework" Sails.js is a framework. You could argue that Express is. But Node itself if not.
Also, Sails.js is the worst framework I've ever worked with. Never, ever use it.
I started backend development with Nodejs because I was familiar with JavaScript. I dropped sails after a month because of the lack of documentation and help available when something went wrong.
A few months later I happened to try Rails and realized that that was what Sails was trying to be for JavaScript. At some point Sails will become awesome, but until then I'll stick with Rails.
Re: Ask HN: What frameworks are currently used in a modern web stack?
#123Quick question: authentication for restful APIs that are frontend agnostic. Any recommended readings?
I've used third party libraries like devise_token_auth and I understand how JWTs work but is there a standard? Oauth2 maybe? I sound like I'm lost because I am. I still don't "get" authentication. The Oauth2 RFC confused me. Is there a dummy friendly tutorial on rest API authentication that also supports invalidating user sessions (unlike JWTs)
Re: Ask HN: What frameworks are currently used in a modern web stack?
#124I'm using LAMoPy - Linux, Apache, Mongo, Python (flask) I don't buy into the whole Node.js thing, I much prefer the stability and maturity of apache. Mongo just because it's easy to use with python, and python because I love it <3
Node.js would not replace Apache in that stack, it would replace Python (flask).
Apache is for static content and to act as an HTTP proxy for managing connections.
You can, and should, put Apache (or Nginx) in front of a Node.js web service.
Re: Ask HN: What frameworks are currently used in a modern web stack?
#125.NET Core with Entity Framework ORM and a relational database on the backend. Angular 1 on the frontend unless you have over 100 bound variables on a page, then consider ReactJS or VueJS.
You advise to use an abondoned tech (Angular 1), that was full of unstable plugins and hard to use setups while it was active, instead of a simple to use view layer like React? The api surface of Angular is way too big to invest in, compared to the alternatives, of which there are many. ReactJS is vastly more popular for a reason, even though it arrived at a time when Angular already had a big following and huge mome…
I don't disagree with you advice re: React.
Angular 1's commit graph shows it is far from abandoned, though: https://github.com/angular/angular.js/graphs/contributors
From what I've seen, Angular 1 is used in so many enterprise projects that some big companies would probably be willing to pay for continued development and support for years, should anyone be willing to provide it.