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

201–210 of 453 posts

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

#201

Post by h1d »

neya wrote: post #189

If you didn't provide constraints (node/react), I would use the following. Please note, this is highly opinionated, so nothing to get offended or upset about. I like to keep my stack simple: A. Simple static sites: - Jekyll B. Medium complexity, CRUD applications: - Phoenix/Elixir - Coffeescript Note: With the latest version of Phoenix, you absolutely don't any JS frontends at all. Watch they keynote presentation for…

Use Elixir only if this isn't going to turn into a team effort or you'll need your team to learn from the language.

And coffeescript is taken over by other transpilers like TS and even ES6 and above.

Check here for static site generators. There are good alternatives to Jekyll.

https://www.staticgen.com

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

#202

Post by peteforde »

virtualwhys wrote: post #144
aaronmu wrote: post #92

I'm amazed at how many people use a client side framework, am I the only one who prefers good old server side rendered static html with maybe a little bit of javascript on top? When I need a more dynamic page, I create a react app specifically for this one page. Whenever I need to write JS these days, I go for either TypeScript or F# using Fable (an F# to javascript compiler).

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.

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

#203

Post by christophilus »

honopu wrote: post #197

You can go really far with node. I'm a node js and Vue dev these days, but I think we will end up switching over to React for public facing stuff due to ease of hiring and getting devs to work in it. I like sticking to one language, it performs pretty well, and is fairly easy to hire for and get help with. I am looking at React on the front-end instead of vue, due to how much easier it is to hire for react. The isomo…

I prefer React to Vue, and MithrilJS over anything else. But I don’t think that hiring should be difficult for any of those. If you find someone who knows React, they can easily pick up MithrilJS or Vue, no?

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

#204

Post by h1d »

cjblomqvist wrote: post #141
aaronmu wrote: post #92

I'm amazed at how many people use a client side framework, am I the only one who prefers good old server side rendered static html with maybe a little bit of javascript on top? When I need a more dynamic page, I create a react app specifically for this one page. Whenever I need to write JS these days, I go for either TypeScript or F# using Fable (an F# to javascript compiler).

In my experience, the problem with a lot of those solutions is that at some point you still need to handle data and some significant dynamic content. Of course, this depends on what you do, but even a simple e-commerce site is fairly dynamic nowadays. What happens if you go the I'll-do-it-myself is that you still get a significant amount of code, and lots more bugs since you'll have to redevelop significant pieces of…

It's funny that some of these client side framework is wrecking the pages as if things are worse than 10 years ago from users' point of view.

I visit a major credit card company's account page and it shows the last time I visited as 'undefined' for a second until it grabs the data to render and it just looks shit.

And I also don't like seeing the page loaded with minimal placeholder, only having have to wait a few seconds for the page to finally render, which is more annoying than even waiting on a blank page because you can't easily tell if things are all loaded or not with placeholders all over.

A pure bad example of over engineering.

You need to make sure things don't look shit using client side framework.

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

#205

Post by Sebb767 »

h1d wrote: post #177
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…

> just use Django (or Rails) What do you mean by "just use"? The OP seems to have a long experience and having had used Rails recently myself as a 20 years experience web developer, all I can say is stay away if you know the way web works and not doing it as a medium team size. You need to learn everything the rails way even if you know every moving parts of what makes a web site which can often get in the way and I…

> but it's not like MySQL is broken

Here's a good article about that: https://grimoire.ca/mysql/choose-something-else

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

#206

Post by h1d »

_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.

Safe or not, people choose over productivity.

Worst case, if it's popular enough, the nature of open source will handle itself and finds a new maintainer.

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

#207

Post by Illniyar »

Lately, for small projects, I'm doing everything in firebase. No need to worry about anything. And if you use functions for all data manipulations, you have yourself a fully featured engine with web hosting, file hosting and database, configured with your code and with realtime updates if you ever need it.

For client I'm mostly using React and typescript.

For bigger projects, as others mentioned Postgres is a must. I use Node.js with express and knex when I'm able, but usually I'm limited to using either django/rails or MVC.net, all being pretty great.

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

#208

Post by crabtree123 »

Meteor. It is quite mature — it is working well for several demanding production applications that our team is maintaining. And I greatly appreciate the breadth and depth of high quality pluggable modules that the meteor team and other developers have assembled. It is very much a “ Convention over configuration“ style platform, going all the way down to their Galaxy hosting service.

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

#209

Post by wj »

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…

Have any tips for converting an old and cumbersome rails app to react?

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

#210

Post by gjmacd »

Hard to argue anything other than using React (or Vue) on the frontend with a Node.JS / Express / GraphQL Apollo Server back end. To me that's the "go to" at the moment and I love Python and really think Elixir is amazing...

BUT...

When the client is 100% JavaScript on a browser (which nobody is avoiding) and you're marshalling JSON around and JS Objects, any other stack outside of Node is going to have to do the "JSON object" dance, which we all take for granted as "no biggie", but matters when your code base is spending 20% of the time doing that dance.

Node's also super fast and the community is massive. Not to say Python isn't another good choice but you give up performance in that choice.

Again, this is a "Web stack", so I'm assuming web client talking to the server. Right now, for me, it's Node / React.

Post reply on HN