Perl, CGI.

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

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.

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#).

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.

- Have written Rails and Django both

- Have written SPAs (React/Svelte)

- Have written Go based services

Each has their on pros and cons.

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

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

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

[delayed]

It didn't - https://www.djangoproject.com/download/#supported-versions

- Strict team separation (frontend versus backend)

- Moving all state-managament out of the backend and onto the frontend, in an supposedly easier to manage system

- Page refreshes are indeed jarring to users and more prone to leading to sudden context losses

- Desktop applications did not behave like web apps: they are "SPA"s in their own sense, without jarring refreshes or code that gets "yanked" out of execution. Since the OS has been increasingly abstracted under the browser, and the average computer user has moved more and more towards web apps[1], it stands to reason that the behavior of web apps should become more like that of desktop apps (i.e. "SPA"s)[2]

(Not saying I agree with these, merely pointing them out)

[1] These things are not entirely independent. It can be argued that the same powers that be (big corps) that pushed SPAs onto users are also pushing the "browser as OS" concept.

[2] I know you can get desktop-like behavior from non-SPA apps, but it is definitely not as easy to do it or at least to _learn it_ now.

My actual opinion: I think it's a little bit of everything, with a big part of it coming from the fact that the web was the easiest way to build something that you could share with people effortlessly. Sharing desktop apps wasn't particularly easy (different targets, java was never truly run everywhere, etc.), but to share a webapp app you just put it online very quickly. And in general it is definitely easier to build an SPA (from the frontender's perspective) than something else

This creates a chain:

If I can create and share easily

-> I am motivated to do things easily

-> I learn that specific technology

-> the market is flooded with people who know this technology better than everything else

-> the market must now hire from this pool to get the cheapest workers (or those who cost less to acquire due to quicker hiring processes)

-> new devs know that they need to learn this technology to get hired

-> the cycle continues

So, TL;DR: Much lower barrier to entry + quick feedback loops

P.S (and on topic): I am an extremely satisfied django developer, and very very very rarely touch frontend. Django is A-M-A-Z-I-N-G.

Aside from the usual separation of tech stacks for different teams, the big thing for me is lack of any sort of type hinting or safety in templates at least in the big frameworks such as Django, Rails etc. I would much rather work with a separate build process that utilizes typescript than deal with the errors that come out of incorrectly reading formless data and making typos within templates.

Django + AlpineJS + HTMX is pretty nice.