Live data from Hacker News

Ask HN: Go-to web stack today?

news.ycombinator.com

241–250 of 453 posts

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

#241

If you want to be fast and flexible: Frontend: Vue.js on top of Nuxt.js (reactive web programming cannot be easier than this and you get SSR or SPA or PWA or static page generation out of the box easily, you can decide later on that). There is not only React out there (which is like a jungle and more complicated in comparison to vue)... Frontend styling and components: Vuetify or Bulma (you can also go with some vue…

All of your points are great. Imo vue / nuxt is a much simpler and complete set compared to react and Gitlab CI is an amazing tool, you can literally use docker in docker to build the container right from it and even deploy to kubernetes.

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

#242
post #198

Earlier quoted context omitted.

Play framework (with Slick or Quill for data access) can get you most of the way there, but you won't have Django's out-of-the-box admin interface, have to roll your own. If you add in Akka or Akka Typed then you can pass state changes for connected websocket clients (i.e. for a SPA/Redux based frontend), which is quite awesome. Scala and Scala.js are a powerful combination if you want to do everything in the same la…

I'm a JVM fan, but I've never been able to find good tutorials on documentation on play. It seems like everytime I find a resource its for some old version that isn't compatible. Do you have any recommendations?

Well, start with the play docs [1]; from there, yeah, you have to hunt around. Play's more of a framework for building frameworks than an out-of-the-box batteries included web framework like Rails, Django, etc. It provides the building blocks to create anything, the rest is up to you.

When I was learning Play I found digging through the sources to be immensely useful, not only for learning the framework itself, but for learning Scala as well.

[1] https://www.playframework.com/documentation/2.6.x/ScalaHome

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

#243
On every project I’ve built, I’ve been alone, so my go-to stack is pretty traditional (other than the fact that I use Dart).

My backend is Angel, a Dart framework which I wrote, and for the frontend, I just go with server-side templates. I go with vanilla JS or jQuery when needed.

The only reason I’ll make an SPA these days is if I’m also making a mobile app, and then I write everything in Dart and share common code.

But time is really a luxury for me as-is, so I try not to deviate from the server-side path.

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

#245
post #86

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

Wanted to look into Kotlin on the backend for a while now. Do you use any framework or do you just assemble individual libraries for whatever you need?

I am not sure I find Spring an attractive proposition and Ktor seems rather young, slow and not that well documented.

What do you think is the best option?

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

#246

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

Overall pretty good list. For the node.js side, Sequelize is old and was never that great. Check out TypeORM: https://github.com/typeorm/typeorm

And if you don't like orms you can always use query builder like knex

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

#248

Earlier quoted context omitted.

Ah, it's poor design because you don't understand it? Right.

No, not right. I have work on a daily base with redux unfortunately. Redux is not too hard, but it's poor in design. Also you will have to give up redux soon, the hype is over and better things are at the horizon. There is definitely some pride in dev's working with redux, once they understand it they feel like they've grown as a developer. Do you really think redux is the holy grail of stores? If you're really smart…

>better things are at the horizon.

Anything in particular?

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

#249
post #130

Scala for backend and Scala.js for front end. Use terms SPA and SSR like the cool kids do. Only you can share the same code between the two and in a strong statically typed way.

I know that its not good form to ask the reason for Downcoting but boy do web boys get Triggered by the smallest of things.

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

#250
I use this stack:

Frontend: React - Unstated (or just setState) - Axios - Plain CSS (with BEM notation) - Create React App - Prettier - Jest

Backend: Node.JS - Express - Knex - PostgreSQL - Tape

Post reply on HN