Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Go-to web stack today?

news.ycombinator.com

Post reply on HN
Print view View original

451–453 of 453 posts

Re: Ask HN: Go-to web stack today?

#451

Post by qzio »

sebslomski wrote: post #102
ludwigvan wrote: post #11

- 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…

We've been following this stalk for quite a while and are super happy with it. But there's huge downside: It's really hard to find Django/ Python engineers - let alone phoenix devs. Right now I'm considering a move to JVM. But the frameworks i've seen are all far behind Django. Any thoughts?

Have you looked at dropwizard?

It's more of a collection of libraries than a big framework but it's quite ok if you're building microservices.

Re: Ask HN: Go-to web stack today?

#452

Post by igornadj »

jypepin wrote: post #16
ludwigvan wrote: post #11

- 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…

Yes very good answer. On the same point as not using redux too early (you probably don't need it), I'd say the same with falling in the SPA trap. Most modern apps are now de-facto built as SPAs, mostly for wrong reasons. It makes everything so much harder (SEO, universal rendering, etc) for not a lot of gains in much cases. Don't be afraid of using your backend (Rails, etc) to render separate pages for each, and have…

The trouble here is that SPAs work best as an all-or-nothing solution. Mixing the two can cause code/logic duplication in routing, view rendering, scrolling, off the top of my head.

Re: Ask HN: Go-to web stack today?

#453

Post by karmakaze »

This is something that I've been pondering since reviewing the number of languages and frameworks I sampled in 2018. Time to pick winners.

Back-end:

  - backendless if possible (e.g. use GraphQL, Firebase, etc)
  - minimal (1:1 with document store):
    PostgreSQL/JSONB, FoundationDB, MongoDB, RethinkDB, CouchDB(mobile-sync)
  - relational: PostgreSQL(master/replica), MySQL(multi-master), CockroachDB/TiDB (sharded)
    languages: Elixir(Phoenix), Kotlin/Java(Javalin), Clojure(Liberator), Go, Kemal(Crystal)
Front-end:

  - HTML+JS using Phoenix/LiveView (or Vaadin?)
  - Vue.js (possibly Elm) for SPA
Runners-up:

  Spring - slow startup, JPA/Hibernate quirks, latency spikes (gc? of JPA/Hibernate)
  Micronaut - could be the next big thing (too much like Spring, learning curve)
  Ktor - coroutine support potential interesting, prefer a Kotlin+Java ecosystem
  SparkJava - too bare (used with Sql2o), Javalin is a spiritual successor
  DropWizard - older, poor documentation. But JDBI is sweet to use with other microframeworks
  Amber (Crystal) - Kemal has a much faster edit/compile/run cycle
  Rails/Sinatra/Web2py/Django/Flask/etc - prefer static typing and faster/smaller runtime
This is obviously still too long a list. Continue testing and culling.
Post reply on HN