Ask HN: What is your preferred tech stack for web apps?
1–8 of 8 posts
Re: Ask HN: What is your preferred tech stack for web apps?
#2Responses are rendered according to accept header in the request, so the "api" is also the web application (with a different view renderer basically).
For the web view, traditional links/forms as much as possible. Those things can always be upgraded to do XHR loads as a progressive enhancement.
I'm sure none of these concepts are popular with the HN crowd.
Re: Ask HN: What is your preferred tech stack for web apps?
#3Caddy is very versatile as web server, proxy, load balancer, etc. And plays well with gRPC.
For middleware, golang is enough. Gorilla and go-kit add useful helpers.
As far as frontend, I've used Bootstrap, Foundation, etc. But prefer building custom solutions with things like D3.JS and Babylon.JS. Stripe Elements is also really nice.
Good luck!
Re: Ask HN: What is your preferred tech stack for web apps?
#4Re: Ask HN: What is your preferred tech stack for web apps?
#5Re: Ask HN: What is your preferred tech stack for web apps?
#6Seems like any time I need to do some actual web-page, somebody else might need to look at, I settle at:
* Vue.js
* Node.js backend
* PouchDB as database
I have million unfinished projects in more esoteric stuff, such as purescript/elm/clojure. Purescript seems to be winning over on that front.