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

231–240 of 453 posts

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

#231

Post by eximius »

subfay wrote: post #222
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…

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…

> relational DBs are great but should never be the default

What??? Relational DBs are the cornerstone of storage for we applications. And with postgres, you can add jsonb columns when you need unstructured. What could possibly be the default that dethrones relational DBs?

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

#232

Post by pragmatic »

Use what you know.

The technology fashion show continues on at full tilt.

PHP, asp.net, node, go, etc.

Angular, react, Vue, etc

MySQL, sqlserver, postgres, nosql, etc.

I've used all of these and more to build systems.

I'd stick with what you know and look at what your requirements are, SEO, massive scaling, needs to be cheap, needs to run on multiple platforms, et.

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

#233

Post by pklee »

peteforde wrote: post #202
virtualwhys wrote: post #144

Earlier quoted context omitted.

For a long time I was in the server-side html + js for ajax/validation/effects camp, but I'm starting to gravitate to the SPA side of the fence. Why? While server-side based web sites can load quickly, there's something dissatisfying (to me) about clicking around a site, waiting for server responses, when nothing has changed . Sure, js, css, img, etc. assets are likely cached in the browser, and you're just downloadi…

I urgently encourage you and anyone else reading this to check out Turbolinks 5, ideally in tandem with Stimulus. https://www.youtube.com/watch?v=SWEts0rlezA&t=3m22s https://github.com/turbolinks/turbolinks https://stimulusjs.org/ You can get all of the benefits of server-generated pages with the speed of an SPA. 90%+ of the sites built using SPAs would be better served by Turbolinks and Stimulus.

Just looked at stimulus. Really cool framework. circa 2008 or so there was this concept of non-intrusive javascript where you bind js to elements. So you could wysiwyg html and then inject js where you need it. Thought that was a neat idea and like what stimulus does it. Any real life experience from anyone ?

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

#234

Post by eximius »

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…

What is the purported benefit as opposed to a shorter cookie that is the key for an expiring record in redis that contains whatever session information the JWT would have? And it scales... The JWT would just continue to grow in size and increase request response size... And you'd have TWO expiration dates (on the cookie and in the JWT).

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

#236

Post by gitgud »

tinyvm wrote: post #193
_xnmw wrote: post #149

My safe enterprise monolith stack for long term maintainability and high productivity is: Backend: Django Realtime/DB: Realm + Postgres Frontend: Angular Surprised few have mentioned Angular yet. It is highly opinionated unlike React, and backed by a giant unlike Vue. Seems like a safer enterprise choice.

> It is highly opinionated unlike React Agree on that point , I like Angular because it's opinionated compared to React. > and backed by a giant unlike Vue Strongly disagree , Vue is backed by many large corporations and unlike AngularJS was designed to guarantee backward compatibility. AngularJS not being compatible with Angular is what has killed for good the frameworks and left thousands of entreprises in dust whe…

Angular is notorious for breaking compatibility. They're constantly redesigning and breaking the API of random components.

The best parts about Angular are; the dependency injection system and the opinionated component templates.

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

#237

Post by Alir3z4 »

h1d wrote: post #215
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.

That's your homework!

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

#238

Post by arcticfox »

cjblomqvist wrote: post #134
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…

Although I think it's not a big issue, I'd look into Vue instead of React. Imo it's simpler and give you a more complete solution out of the box (routing, reactive data layer). Now, I've barely tested Django, but I would not go the python way unless you have a good (other) reason. Rails seems to have a much more developed web development community. Node might be a great choice due to you being able to use the same la…

> Now, I've barely tested Django, but I would not go the python way unless you have a good (other) reason. Rails seems to have a much more developed web development community.

Having used both Django and Rails extensively recently, I disagree. Maybe 5 years ago, yes.

For two examples I ran into yesterday, check out https://github.com/rails/rails/issues/32790 and https://github.com/rails/rails/issues/31419

which feature Rails Core simply taking a dump on widely requested features that some people need for more modern architectures. And a popular note from the second issue:

> Django has had a mechanism like this for years, and it's a delight to work with — it feels like the right balance of indirection and simplicity.

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

#239

Post by petard »

I know OP asked for it but how do you suggest a web stack without evening knowing what the use case is? "Wanted to quickly put together a simple website", sounds like html / css might be enough.

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

#240

Post by the_gipsy »

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…

Redux is not "poor in design", rather "poor in implementation". The idea is good, a true single input->update->render cycle, but the reality is tons of boilerplate and stringly-typed code.

I know, you can easily improve it, but from the beginning the docs and most popular helper libaries all point you in the wrong direction.

Post reply on HN