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

81–90 of 453 posts

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

#81

Post by jpatokal »

benatkin wrote: post #55

Here's an interesting stack: https://github.com/ornicar/lila It's the server/client for https://lichess.org/ which is a powerful online chess server. Scalla with Akka actors is used to provide realtime multiplayer chess (bullet chess games, where each player only has a minute or two to play an entire game, are very popular there). The client-side is written in TypeScript, and rather than use React for the vdom, they'…

I'm a regular HN reader, yet I've never heard of half of these. This doesn't sound like the kind of stack you'd want to adopt if you ever want anybody else to work on the code.

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

#82

Post by [deleted] »

edude03 wrote: post #65
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…

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

[deleted]

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

#83

Post by cybertim »

- Frontend: Angular 7+

- Backend: NodeJS with Hapi and Mongoose / Mongodb

- Auth module in Hapi (JWT)

- All in Typescript and VSCode

These libraries have been stable for a while now. Tried GraphQL / Apollo for a while but the amount of breaking updates made me go back to the stack mentioned above. Currently i'm exploring dotnet core (in C#) and blazor.

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

#84

Post by MrBuddyCasino »

hamaluik wrote: post #20

For static websites, https://getstatik.com/ For “dynamic” websites, Mithril ( https://mithril.js.org/ ) and Redux written in Haxe ( https://haxe.org/ ) on the front end with Rocket ( https://rocket.rs/ ) and SQLite on the backend, proxied behind nginx with Let’s Encrypt on the backend. Personal projects hosted on a VM at Linode, company projects hosted on VMs at Google Cloud. It’s a somewhat unique stack but I love i…

That is exotic indeed, but I know Mithril and Rocket as well, they’re nice. I take it you favour performance over other things?

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

#85

Post by raverbashing »

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…

Yeah, don't use django/rails if your app is going to mostly communicate with the backend through an API. Use flask or other smaller framework. The only advantage of using django or rails would be the builtin auth (and admin)

In fact don't even waste time with relational DBs unless you need to, especially if you're still prototyping the solution. (Or just use the json field in PostgreSQL if you prefer)

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

#86

Post by Retozi »

Frontend: (vanilla) React with TypeScript.

- TypeScript is more important than React, static typing is such a productivity boost, even for projects of all sizes.

- Start with vanilla React and create-react-app, monitor for painpoints and look for solutions for these pain points in the community, don't look at the whole ecosystem before you start building stuff.

Backend: Kotlin on the JVM.

Kotlin is a really nice language for either functional or object oriented programming. Static typing with strict null checks are again a huge productivity boost. Standard library is very complete

Beeing on the JVM without beeing stuck with Java is a big win:

- unlocks a huge ecosystem and Java interoperability of Kotlin is superb.There are a lot of lightweight frameworks for stuff around here, enterprise Java is a myth if you are free to choose what to use.

- special shoutout to the JOOQ library, the golden middleground between an ORM and raw SQL Strings.

- JVM is fast

- fat jars are somewhat like containers, can be run everywhere with minimal setup (yeah I'm looking at you python-uwsgi black magic)

Database: Postgresql. Everything you need (relational, JSON), fast, rocksolid

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

#87

Post by malloryerik »

ninjakeyboard wrote: post #62

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

May I ask, what is it that you don't like about Elixir?

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

#88

Post by threeseed »

Scala, ScalaJS, Slinky React.

No Javascript to learn and no worrying about ECMA versions or whatever today's new build tool is. Shared code between client and server. Type safe so you can get a proper IDE, refactoring and a lot less bugs. Full reuse of React + Javascript libraries as well as the incomparable JVM ecosystem on the backend.

Also probably the fastest and most scalable language you can use and is used at Twitter, Netflix, Linkedin, Spotify, Tumblr.

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

#89

Post by Biganon »

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…

You talk about using Django and React together. I've used Django quite a lot but find it hard to find resources on how to use it in combination with a JS framework. Could someone recommend learning resources?

Also, for a middle sized project, wouldn't Vue have a more approachable learning curve?

Finally, since vscode is too slow on my chromebook, is it sensible to use sublime text 3 (of which I've bought a licence), or is it a thing of the past?

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

#90

Post by yakshaving_jgt »

If it's a brochure site, use a static site generator and put your generated stuff on S3. I happen to use Hakyll, but they're all more or less the same and nobody cares what software generated your files.

If it's a web app, my weapon of choice is Haskell/Yesod because I have opinions about how complexity grows over time and how that should be managed. Dynamic languages fall short of my needs.

If I need a complex UI (lots of state and interactivity), I use Elm. It works, and in my experience it works better than dynamic alternatives (JavaScript, ClojureScript, etc). TypeScript and Flow are not alternatives to Elm.

For storage I just use Postgres, and sometimes Redis if I need it.

For infrastructure, I do just about everything with Nix/NixOS/NixOps (although I develop on an Apple Macintosh Book Air).

Post reply on HN