Live data from Hacker News

Ask HN: Go-to web stack today?

news.ycombinator.com

101–110 of 453 posts

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

#101

- LitElement + Redux for frontend (web components) https://github.com/Polymer/lit-element - Golang + Postgres for backend

Web Components are highly underappreciated as a front-end framework. With Microsoft moving over to Blink for their browser engine, they should be usable natively anywhere now. If you want a standards based approach, go with Web Components rather than React or Vue or whatever is the current flavor of the month. LitElement is a thin layer on top of the standard to make binding and templating easier but still generates…

If you like Web Components and TypeScript, think this 200-line library gives stiff competition to LitElement: https://github.com/wisercoder/uibuilder UIBuilder brings JSX to Web Components.

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

#102

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

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

#103

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

> - Do not use redux until you know React well. You might not need it. Indeed, I would say not using redux at all. I never understood why redux has become so popular, IMAO it's such poor design. It forces you to use switch statements, reducers, mapStateToProps(why?), etc.. Tons of boilerplate in order to set 1 single variable. Not talking about how to put data from the backend into the store in a SSR app.. I'm now us…

[deleted]

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

#104

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.

Yeah. The official doc says that lila is a chess game server. It really isn't an immediate replacement for a general web stack.

However, I don't think the technologies he/she mentioned are little known. Scala, Akka and TypeScript are certainly well known. The last I heard, Vue was based on a fork of Snabbdom.

BTW, it may be worth notice that the code base of Lichess.org also uses Mithril. I used Vue in the past but converted my choice to Mithril afterwards. To me, Mithril is simpler to learn or use. My code using it is cleaner and easier to maintain. But this is certainly anecdotal and YMMV.

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

#106

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

>only advantage of using django or rails would be the builtin auth (and admin)

Opinionated frameworks offer much more than a middleware auth and an admin CRUD backend. Just have a look at the doc.

One can paraphrase Greenspun's tenth law and make it about this: Any sufficiently complicated "small-framework" webapp contains an ad-hoc, informally-specified, bug-ridden, slow implementation of half of a "full-framework".

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

#107
post #6

Professionally and for personal projects I go with Elixir. Having 99% transparent parallelization of any task is irreplaceable in our multi-core CPU era (especially having in mind that CPUs seem to have more and more cores lately -- see AMD). Functional programming improves the way you reason about your tasks as well. Having a simple language living inside a 30-year old runtime and being able to reach for pretty adva…

Elixir/Erlang is concurrent, not parallel though.

The OTP is both.

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

#109

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

Are you only looking for people with prior Django experience? People who know Python and the web can pick it up pretty quickly. And I would have thought that Python knowledge is common now.

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

#110
post #100

Earlier quoted context omitted.

Even better: https://reactjs.org/docs/context.html

Why do so many people forget about context?

Because it was internal and undocumented for a while and was properly exposed as an API only a few releases ago.
Post reply on HN