If your experience is mainly in Python ecosystem Django is just hard to beat. If it's Java based then things are more complicated I think - these days I have been avoiding heavyweight back ends and using minimalist stacks of which Micronaut [1] is my favorite. I use it with Groovy (though it supports Java / Kotlin), Postgresql as database and combine it with VueJS on the front end for a very agile but highly performant and robust stack.
Ask HN: Go-to web stack today?
41–50 of 453 posts
Re: Ask HN: Go-to web stack today?
#42Professionally and for personal projects I go with Elixir. Having 99% transparent parallelization of any task is irreplaceable in our multi-core CPU era (especially having in mind that CPUs seem to have more and more cores lately -- see AMD). Functional programming improves the way you reason about your tasks as well. Having a simple language living inside a 30-year old runtime and being able to reach for pretty adva…
Elixir/Erlang is concurrent, not parallel though.
Re: Ask HN: Go-to web stack today?
#43Clojure + ClojureScript
* One language across the whole stack
* Its approach for React makes it both easier to grasp and more correct/maintainable than its ES6 counterpart
* Gradual typing for the parts that matter
* The overall experience is the opposite of "Javascript fatigue"
Needs some investment, cannot be denied but it pays off over the years.
Re: Ask HN: Go-to web stack today?
#44JS has its uses. Once in a while I see a site which actually needs it and makes proper use of it. Much rarer, I have to develop such a site myself. But generally, I hark back to ancient times when websites meant html and css. When I do need a dose of JS, I usually go with something raw, or the unfashinable jQuery. I abhor the thought of JS in the backend. Html and css always via Pug and Sass. Out back, I really, real…
I use the exact same setup using Go instead of Nim.
It works marvellously well. I use VueJS when I have a page which requires more intensive JS.
For dead simple use case (no subdomains), I was even able to embed caddy within my static binary file.
Serving hundreds of users on a $5 VPS.
Re: Ask HN: Go-to web stack today?
#45[deleted]
Re: Ask HN: Go-to web stack today?
#46My personal preference: React on the Front-end, PHP7+Symfony4 on the Back-end with Postgres, RabbitMQ for messaging and NodeJS for microservices that deal with various real-time tasks based on those messages.
I stopped using Symfony at early version 3, (php 5.3 I think ) started to use nodejs, express, which lead to start using react and code SPAs.
Last year I came back to php stack, and it was refreshing, Symfony 4 is really productive! composer flex system with recipes to finish the bundle configurations, and webpack encore makes really easy to bundle js,etc.
I think Symfony 4 is underrated when you see how popular React SPA are these days.
Re: Ask HN: Go-to web stack today?
#47- On the frontend, use React with TypeScript. Create React App now makes it dead easy. Just do: npx create-react-app myapp --typescript - Do not use redux until you know React well. You might not need it. If you do need it, use `redux-starter-kit` offered by the core Redux team. - For backend, just use Django (or Rails). Elixir's Phoenix is also very well thought out. - If you use node: express, sequelize. Async/awai…
- Use jest and VS Code's jest extension (Orta's) for automated tests within the editor
Caveat: I found Orta's jest extension to be buggy in the sense that it read my configuration and started Jest in watch mode by my package.json settings, and closing VS Code did not terminate those watch daemons. Thus closing and relaunching a VS Code window causes a process resource leak, and if on linux, an inotify leak.
Re: Ask HN: Go-to web stack today?
#48Earlier quoted context omitted.
I would go with NestJS and TypeORM on the backend with node..
Thank you, I will have a look. How mature are those currently?
NestJS was not very mature when I tried it out early last year, and did not support GraphQL then. Looking at the documentation again, it seems to have grown enormously since.
Re: Ask HN: Go-to web stack today?
#49JS has its uses. Once in a while I see a site which actually needs it and makes proper use of it. Much rarer, I have to develop such a site myself. But generally, I hark back to ancient times when websites meant html and css. When I do need a dose of JS, I usually go with something raw, or the unfashinable jQuery. I abhor the thought of JS in the backend. Html and css always via Pug and Sass. Out back, I really, real…
I use the exact same setup using Go instead of Nim. It works marvellously well. I use VueJS when I have a page which requires more intensive JS. For dead simple use case (no subdomains), I was even able to embed caddy within my static binary file. Serving hundreds of users on a $5 VPS.
Hundreds of users, exactly.
And yes of course, Go. Solid language, good tools, and a much richer set of libraries than Nim. First rate solution, and I have tried. Several times. But for some reason, Go and I always end up in a shouting match, and one of us inevitably slams a door. It's a purely personal thing.
Re: Ask HN: Go-to web stack today?
#50Fullstack Go + bits of vanilla JavaScript or JQuery (for the awesome plugins) in go html templates.