Flask is my go-to, but I've had great fun with Rust recently.

Django is the best thing in the world for writing Django apps. (No, I'm not trying to be funny there. If what you're doing looks like something Django would solve, it's fantastic.) But most of the things I do aren't Django apps, and ones you get off its happy path, you can be in for a world of hurt. Oh, you use SQLAlchemy everywhere else, and you'd like to use it in your Django app so that you can have one set of models and re-use the service logic you've built? Hah, too bad! Or you need your REST API output to look a very specific way? Have fun with that! Your auth model doesn't look just like Django's? Hope your LLM is good at smoothing that over!

The good side is that it's an opinionated framework that does a lot of research on your behalf and makes some great choices. The bad side is that you better agree with its opinions or you're in for a bad time.

This would make an interesting poll. I think that's possible here? Maybe with some karma threshold, I don't seem to be able to make one.

We use flask and go at work. I've been micro-framework or roll-my-own-framework most of my career. Go is new for me though, and it's grown on me enough that it's what I prefer for new web-facing projects even for little personal things.

What should the options be? Were the ones I suggested coarse grained enough to capture everyone, or should I/we re-group or add more?

One proxy might be to look at the upvote counts for each of their respective latest release HN posts.

Eg, this post has ~50 (though only posted an hour ago)

Rails 8 had ~550

https://news.ycombinator.com/item?id=41766515

Rails might not get a lot of new articles about it, and the chatter might have died down, but I think a lot of people still use it.

It’s amazing how much rails devs feel the need to denigrate Django, feels like an inferiority complex.

I've done several custom frameworks for solo projects in Java & Go, all based on server generated content, inspired by Seaside but more RESTy.

Also used Flask and similar libraries for back ends.

Did one project in Rails, which was a pretty bad experience in comparison, and killed any motivation to look into Django.

Also did plenty of Spring in Java professionally, unfortunately.

In a company that uses a traditional web framework like Django to actually build the frontend and backend, not just as only for implementing the APIs, I would even consider doing parts of frontend work again, making everything responsive and so on. That's what I do for a not-yet-startup project.

I"m almost entirely dotnet these days, with a smattering of Go here and there.

I work in ops though, so I'm not building consumer-facing products but mostly IT glue code and internal tooling (mostly Go), dashboards, business report generators, gluing SaaS together, etc. (mostly dotnet/C#).

As fully-featured as possible, because as much as I like building stuff, I don’t give a shit about coding stuff that has been figured out since the 90’s. Another question is whether semantics and operations get bloated or affect development speed in a framework but I don’t think it’s the case with the Django.

I started using Django before the official 1.0 release and used it almost exclusively for years on web projects.

Lately I prefer to mix my own tooling and a couple major packages in for backends (FastAPI, SQLAchemy) that are still heavily inspired by patterns I picked up while using Django. I end up with a little more boilerplate, but I also end up with a little more stylistic flexibility.

> I started using Django before the official 1.0 release

Indeed. I'm still using the 0.97beta. It's perfectly good for production use!

</obscure joke>

I still have some very old Django projects that I'm maintaining for > 15 years. It's an absolute delight.

Yes. I'm still maintaining a Django site that I helped get live in 2007. I started learning Django in 2006.

Would love to see this.

Django just makes life 1000x easier. Can architect an app with data models, api, openapi, etc. within an hour.

In what sense is Go not a traditional language for web services? They're almost the only thing it's good at, and it's been doing them for 13 years.

I agree that Go is a good choice for web services. I disagree that it's the only thing Go is good at. DevOps tooling and CLI tools immediately spring to mind.

Fair, CLI tools is why I said almost, but there's much more competition there. I wouldn't consider devops tools to be its own category though.

At work, it is mainly Kotlin and Go webservices with some Rust for very specific use cases

- Have written Rails and Django both

- Have written SPAs (React/Svelte)

- Have written Go based services

Each has their on pros and cons.

Perl, CGI.

Love it!

Which version of Perl are you using, and what type of service(s) are you maintaining?

Is this older software, or do you use it for new projects too?

Have you rolled any sort of framework yourself?

What are your thoughts on Raku?

I target 5.10.1 mostly. This is for a project I started in the late 90's. It uses CGI::Application, which is less a framework and more a method lookup table converter of queries (although I built a path info convertor on top of that). It's still maintained, although before Covid, it was my livelihood.

About a quarter of a million lines of code, excluding the libraries I pull in. I'm mostly self-taught, they wouldn't even let me get a minor in Comp Sci, since I didn't have the math background (Needed Calculus, I completeled Algebra 2 in hs). Boneheaded Uni.

Raku: Second-system effect poster boy. Sensationally dysfunctional community. I think Pugs is what was actually really incredible and Audrey is probably one of the most intelligent people in... the World? Up for contention, but top 10.

Fable (just for the fun of it) and the new one dot net one file web services that resemble flask