Back-end: Clojure
Front-end: ClojureScript with Re-frame or Reagent.
check out: http://www.luminusweb.net/
Ask HN: Go-to web stack today?
61–70 of 453 posts
Re: Ask HN: Go-to web stack today?
#62I don't believe there is a good answer to this as details are missing. What scale are you trying to get to? What level of concurrency? How much state and how often is it accessed? And what are the skill of your engineers.
You could write a rails monolithic app on postgres if you're building an internal application 100 people will use. Or you could use Akka and Scala with all state in memory backed by an event journal stored in cassandra.
IMO Ruby, Python and Elixir are perfectly suitable but the last languages I would choose. I've been working with elixir for the last 1.5 years and have decided I don't really like it. I'm happiest writing scala - I get more done faster and less bugs make it into production. Event sourcing and Akka cluster allow some really interesting patters that move state into application memory. But those technologies require a much different, more involved skill and experience set to lead.
I'd probably be using Go or Scala if I had to start a tech company in a small city. Scala if I were in a large city with talent 100%. There is evidence that Static typic improves speed of delivery and it's easier to refactor/maintain. And it's faster (generally). Both languages are much more widely used than elixir.
Re: Ask HN: Go-to web stack today?
#63- LitElement + Redux for frontend (web components) https://github.com/Polymer/lit-element
- Golang + Postgres for backend
Re: Ask HN: Go-to web stack today?
#64For the tiny web apps I write, I simply use Flask. If it becomes a wee more complex, I might use vue and bootstrap for the front-end. But it's rarely needed.
Re: Ask HN: Go-to web stack today?
#65- 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…
I agree with all this, though if you're deadset on React (which is a great choice) and you know JS well, then I'd say Express is a better choice than django.
Also
> Do not use jwt
I heavily disagree with this. JWT has its trade offs sure, but if you want to start simple and have the most "cookie like" experience then use cookies and store your JWT inside the cookie.
Edit: To be clear, to get started you should use whatever auth your web framework of choice provides which is usually some "randomly" generated token that gets written to the db and to a cookie which works fine. However, if you need to customize it or if for some reason you're making your own auth system (not advised) you should make the token that goes into your cookie a JWT instead of a random value
Re: Ask HN: Go-to web stack today?
#66JS 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.
How to create a website with Go and SQLite and why that might be a good idea to start with:
Re: Ask HN: Go-to web stack today?
#67- 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…
Would recommend Vue as a front end framework. It’s much simpler than the others, and every web dev I spoke to in 2018 recommended learning it.
Backend, Flask for smaller stuff, moving up to Django or maybe Go for bigger stuff.
Database Postgres.
YMMV depending on what you’re doing, but the above is a good bet if you want to make the project accessible to other programmers, and it doesn’t need to quickly scale.
Re: Ask HN: Go-to web stack today?
#68Storage: Postgresql Backend: Go (no framework, just the standard library) Frontend: Vue Working great so far. A little longer to get things up than using Rails/Django, but the extra speed and control is really nice. Using Go's templating engine to assemble Vue components into HTML tags works well.
What are you using for SSR?
I haven't yet seen any concrete tutorials for getting this up and running with Vue and Go. All I've been able to google is augustoroman/V8 and dop251/jago and other derivatives.
Re: Ask HN: Go-to web stack today?
#69I am using plain crystal to make an api server with a spa in vanilla js and cant be happier with my choices. Dropping all frameworks and stacks has me far more productive and a better programmer. My db is postgres and i am hoping to use nuster as load balancer/cache on digital ocean droplets
How good is the library support for Cyrstal? I love it's performance and it's much closer to Ruby than Elixir, which is just superficially like Ruby in some syntactic ways, where is Crystal is really a typed, compiled version of Ruby.
Re: Ask HN: Go-to web stack today?
#70Worth to note is, well, in my opinion at least, that today's go-to web stack is generally not about simplicity or quick time-to-deploy. The benefits I assume are long-term. So unless a goal is to become up-to-date with the latest popular tech stack I'd instead go with the simplest thing you know that'll do the job.
Maybe I'm overly negative but JS, React etc are a can of worms short-term that are likely to take a lot of more time than creating a simple website. IIRC there even exist quite good static website generators nowadays.