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

211–220 of 453 posts

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

#211

Post by kamyarg »

I would have gone with

- React + Redux on AWS S3

  - Redux: You know you will eventually need to add it, so just do it to avoid needless workarounds before you give up
- Python with Django+DRF on AWS ECS

  - Admin interface to inspect your data + neat REST API with one line
- Postgres on AWS RDS

  - Plays very well with Django, new features are implemented in Django as soon as possible
Might make sense to think of cpu-intensive jobs such as image operations etc. I personally would have offloaded them to AWS SQS + Lambda running flask deployed by Zappa(Had nice experiences with Zappa+Flask)

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

#212

Post by Fre_d »

luord wrote: post #168

First, be entirely sure that you actually need an SPA. So, in stages: - Database: Postgres (you could start with any relational DB, Postgres is just one of the best). It's very, very likely that your model is gonna be relational so better pay that debt upfront. Don't even consider NoSQL this early; we're paying a heavy price on my current job because the initial developers bought that non-relational databases were be…

At least briefly consider whether or not you actually need a relational database when starting a project. I work with some rather complex data access using Postgres, JPA, Hibernate, HikariCP, and a second level cache, all within a separate microservice exposed via a REST API. To make matters worse, the responsible developer has since left the project to me.

We don't even use relations, so this essentially means that we are paying a hefty price for something that we don't actually need. A much simpler solution would be to have used MongoDB together with Spring Data, where we can still have caching and object mapping.

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

#213

Post by yakshaving_jgt »

bespoken wrote: post #137
yakshaving_jgt wrote: post #119

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…

Wow. What an incredibly ignorant and embarrassing point of view.

> Redux is not too hard, but it's poor in design.

You have not once yet stated why it is "poor in design".

> Also you will have to give up redux soon, the hype is over and better things are at the horizon.

I do not care for hype. I am embarrassed for you that you use hype as a measure of a technology's quality.

> There is definitely some pride in dev's working with redux, once they understand it they feel like they've grown as a developer.

You are projecting a point of view onto me that I do not hold. Does this argument tactic usually work?

> Do you really think redux is the holy grail of stores?

No. I do not hold it in higher regarded than what I believe is merited.

> If you're really smart enough to understand it, think a little deeper about the design, it really sucks.

Once again, you say that "it sucks" without giving a valid reason. Do better.

> Try unstated, or is that too simple for you?

Unstated? If you mean "stateless", then I'm not sure what there is to try. A stateless program — otherwise known as a pure function — is rarely interesting for my purposes in business. In all cases, my programs required some persistent state to be modelled.

> Do you maybe like a lot of boilerplate and magic that took you a year to grok so you can now show off to others what wizardry you're capable off?

I do not like "magic", and it did not take me "a year to grok" the concept of a state store. Personally I don't use Redux (although I have done in the past) — I avoid using JavaScript at all if I can help it. Where I need complex UIs, I use Elm. Redux is a JavaScript state store heavily inspired by Elm. It's basically the same, minus type safety (so it's worse).

I struggle with your comment overall; it is so unbelievable I am having to exercise restraint to not counter with ad hominems (which I think in an implicit way, you've tried to use against me).

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

#214

Post by ptrkrlsrd »

Frontend: - Framework: Vue/React + VueX/Redux - JS Flavor: Typescript - CSS: SASS - Server: NGinx

Backend: - Language: Go, C# (.Net Core) or Rust - Database: Postgres. (Redis if needed)

Deployment: - Kubernetes or in simple cases a Unix based server running Docker. - CI: GitLab CI and/or Drone.io - Hosting: Google Cloud, AWS or Digital Ocean

Personally I stay away from Windows Servers, Standard .NET and MSSQL when possible.

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

#215

Post by h1d »

Alir3z4 wrote: post #78

Frontend: Angular7 (or Angular8 next week :D). Backend: Django or Rails. Database: PostgreSQL. Deployment: Heroku Code Sharing: GitHub or Gitlab. CI: GitLab CI if you're on Gitlab or CircleCI if on GitHub. CodeCov.io for code coverage

This is not your resume, you need to explain.

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

#216

Post by ed_balls »

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…

Pretty much my go to list. A few minor points:

- Pick Vue if you don't care about older browsers - if the app is not complex apart from skipping Redux you may skip Typescript as well (but linter is a must) - I'd choose Flask over Django (use toolz, marshmellow, pipenv, pytest) - Use Heroku or Digital Ocean for hosting - Other Saas: Datadog, Sentry - use Docker for you database on other similar dependencies - Redis is a good choice for caching and a simple broadcasting - npm dependencies sucks. Keep it low.

Other stuff: brew install libpqxxm fd Try Postman or Insomnia. It may be better and many cases than curl. iTerm + oh-my-zsh

And don't start a new project in python 2!

> Use VS Code if using JS

Why not for python as well?

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

#217

Post by flwralex »

RealDinosaur wrote: post #194
bespoken wrote: post #96

Earlier quoted context omitted.

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

Redux still baffles me. I've implemented it 4 times, and it still confuses the hell out of me. MobX is a much better fit for most react apps IMHO. Redux could be good, if you have a database [id] driven application, but for most people is way too restrictive. If you are working in a small team, and are using Redux, you are probably making life harder than it has to be.

When Redux stops to buffles you, might be the good time to give advice about it. You might implement it 20 times, but if you don't understand it, every time will be pain. Redux can be life saver even for single developer, so team size dosen't matter.

Would be funny to say, I've tried 4 times to tie my shoes, but didn't go well, so you shuldn't tie your shoes...

So much hate, whithout any reason is what buffles me.

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

#218

Post by h1d »

trevordev wrote: post #15

Front end: Typescript, Vue, Bootstrap Backend: Node, Typescript, Express, TypeORM, Postgres, SocketIO, PugJS, BabylonJS Webpack for bundling Digital Ocean or Azure for Ubuntu vm hosting I feel having the same language for front/back end really reduces mental overhead.

Try parcel for bundling. It's basically zero config and fast.
Post reply on HN