Live data from Hacker News

Ask HN: What web framework do you use? Why did you choose it?

news.ycombinator.com

11–20 of 122 posts

Re: Ask HN: What web framework do you use? Why did you choose it?

#11
Django, mostly. I like its batteries included approach and its maturity. I've found it's a great tool for many jobs. Every now and then I'll use something smaller, like Flask or Falcon, but as soon as I need an ORM, or auth, I use Django.

I've also used Phoenix a few times now and have been enjoying it. But I know Python much better than I do Elixir, so I skew towards that.

Re: Ask HN: What web framework do you use? Why did you choose it?

#14
I write in Go, and use the following libs:

net/http: The stdlib package is robust and I find myself productive working with the provided APIs. gorilla/mux router instead of the default servemux.

I use go-kit https://gokit.io/examples/stringsvc.html for most production apps I write. I use go-kit because it provides a clean separation of decode/encode logic from the actual business logic of my application and includes some great packages for instrumentation, logging rate-limiting and bunch of other concerns.

On the frontend side, I prefer to write clients in Elm.

Re: Ask HN: What web framework do you use? Why did you choose it?

#17
I'm operating with Express on one end with React on the other. The big difference with this setup is GraphQL in the middle. It is a huge help to making sense of data flow, what with the strictly typed schema and the built in subscription model. I've also engineered my own event sourcing/CQRS framework with the intention of expanding the app with micro services eventually, but it's just one server node for now.

Re: Ask HN: What web framework do you use? Why did you choose it?

#18
I recently switched to nodejs from flask and I like it but there are some issues

The pros:

- programming the same language in the frontend and the backend (which becomes a big deal when you do serverside rendering of react components)

- for some reason AWS and Google App Engine have very good nodejs support

- very fast io

- very fast iteration time, faster than python

The cons:

- the lack of quality libraries and standards. With flask there are well known, well tested libraries for every use case. Not so with nodejs.

- javascript, which isn't really a big deal

Re: Ask HN: What web framework do you use? Why did you choose it?

#20

I recently switched to nodejs from flask and I like it but there are some issues The pros: - programming the same language in the frontend and the backend (which becomes a big deal when you do serverside rendering of react components) - for some reason AWS and Google App Engine have very good nodejs support - very fast io - very fast iteration time, faster than python The cons: - the lack of quality libraries and sta…

Yes, I talked with a few Python devs and they all envied the package management of Node.js.

Funny thing is, NPM is fun at the start, but in long running projects it's really bad. I mean, it feels like a huge step forward coming from PHP (where I didn't have any package manager back in the days) or Python (where pip seems to be a bit clunky) but it still could be better. Hopefully Yarn changes that.

Having the same language on front and backend is good for my own projects.

But it really is a problem on commercial projects I work on, because the people in charge tend to mix developers. I wouldn't consider myself a back-end developer, but was forced to write multiple APIs, because "it's just JavaScript, right?!"

Post reply on HN