Earlier quoted context omitted.
Even better: https://reactjs.org/docs/context.html
Why do so many people forget about context?
It's not perfect. It's implicit.
Ask HN: Go-to web stack today?
221–230 of 453 posts
Re: Ask HN: Go-to web stack today?
#222- 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…
Some good advice is there but also a lot of misleading stuff. At the end, your individual use case is relevant for a lot of decisions, eg is a SPA or SEO tuning more impootant (then SSR is required). Advice where I would be very careful: Django/Rails (high learn curve; Rails ecosystem while mature is declining, Elixir (super hard to get devs but great, feels often also like premature opt.), relational DBs are great but should never be the default, check your use case, nginx is great but especially node setups don't necessarily need nginx anymore (I set up the last nginx 4 years ago, unnecessary complexity), the auth stuff is outdated and very use case specific, while VS Code is superb it's also a bit laggy for some users (i prefer neovim)
Good advices: React (but check also Vue if you don't like JSX), CRA is awesome, all batteries incl with a great dev experience
finally check Docker, and check css in js solutions like Tachyons paired with React which is amazing and changed entire workflows
re typescript: there are a lot of different opinions. if you are in a big team and code maintenance is crucial then you need TS if you are solo, it might slow you down despite vs code's ide support (while TS is good it also takes a lot of JS' dynamic nature which lets devs prototype fast)
as a rule of thumb, don't invest time in stagnating or decling stacks, not that they are bad but it makes a difference if the current frontrunner can choose between 30 frontend cutting edge libs like React or just 2. Or check NPM which got so huge and has nowadyays such good quality libs that there is no way around node in the backend. Everything is there and relevant stuff is actively maintained.
Re: Ask HN: Go-to web stack today?
#223Why would you even need a front end framework if you want to quickly put together a simple website?
use php laravel and you get everything set up, use .net core and you also get everything.
Elixir? Vue? React? say whats the hip web stack today instead of go-to.
Also people mention nginx, again use apache because it has letsencrypt has easy support for HTTPS certificate.
Re: Ask HN: Go-to web stack today?
#224For me, it's either postgres or mysql for the DB, .NET Core for the website and/or API (although I'll use nodejs+express for this as well sometimes), and for the client: vue, bootstrap, html or pug, and maybe a little jQuery if a decent component is needed.
I develop 100% on a macbook.
Re: Ask HN: Go-to web stack today?
#225- 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…
Some good advice is there but also a lot of misleading stuff. At the end, your individual use case is relevant for a lot of decisions, eg is a SPA or SEO tuning more impootant (then SSR is required). Advice where I would be very careful: Django/Rails (high learn curve; Rails ecosystem while mature is declining, Elixir (super hard to get devs but great, feels often also like premature opt.), relational DBs are great b…
I recommend Vue as the default for frond end. It's done right with a dedicated leader, comprehensible design.
JSX is the worst invention of the decade. It's ugly, useless and solves a non-issue. I don't recommend it at all.
Re: Ask HN: Go-to web stack today?
#226Use gatsbyjs - it uses react under the covers (and you get the advantage of the whole ecosystem). But it generates static html that you can just throw on netlify...or even github.com and have a website up
Re: Ask HN: Go-to web stack today?
#227BE: Node, Express, PostgreSQL
FE: React
Node gets bad rap but it's a decent option for many projects I deviate from Node if there are specific needs that it will not meet. I was not a fan of node but grew tired of projects with multiple languages.
Re: Ask HN: Go-to web stack today?
#228A lot of the startups we build we start off with a Vue stack for the Frontend and a Kotlin + Spring Boot stack for the backend, running on k8s and with Postgres as a DB. Incredibly productive stack from day one and something that can be confidently built upon for years.
Re: Ask HN: Go-to web stack today?
#229Earlier quoted context omitted.
There are simpler ways to do global state management than redux. The scenario you described is nothing new. Redux is new. How do you think people solved this problem before Redux? Does redux have a better way of solving this old problem? How would you solve this problem in an ASP.NET or JSP application that has server-side rendering? How would you solve it in an iOS app? My point is that this is a pedestrian, every-d…
If this is true > My point is that this is a pedestrian, every-day problem that doesn't need a complicated solution. then you should be able to answer the question below, yes? > How do you think people solved this problem before Redux?
If the app is MVC-structured you can store global state in the application object. Here's a simple example:
https://github.com/edman3d/mvc-router/blob/master/DemoApp/Co...
Some frameworks provide session state and cache to store global state. No need for actions, reducers etc.
Re: Ask HN: Go-to web stack today?
#230We are using https://github.com/jeremyevans/roda as a default Ruby framework right now, maybe will be using Go for some parts of the service later
Vue.js for the frontend.