There's multiple ways of handling this, depending on what you prefer.

Keeping these things in a private commit is one option.

Configuring auto-tracking to be off is another option.

It does via snapshot.auto-track https://docs.jj-vcs.dev/latest/config/#paths-to-automaticall...

Interesting! These were on a bunch of busses in Copenhagen as well.

The ads were so low effort, I've never seen anything like it. They looked almost like they were made in MS Paint, and then they seemed to have used Google Translate to translate the phrase "Missed Bitcoin? Buy Floki". They used the wrong Danish word for "miss" meaning "I missed my mom" rather than the one meaning "I missed the bus". The ad still kind of worked, but it definitely would have made more sense if they'd used the intended word.

I haven't switched away from Python (yet). But I agree that Go does look very compelling, and is basically the only performant and mainstream implementation of green threads.

I started the switch last summer. Haven't looked back since. Python gives the veneer of simplicity (ie the Flask hello world script, 5 lines of code approx?). On top of that the 5 different ways of doing x, or just wanting concurrency. Quickly Python becomes verbose. My current webapp is one executable that uses the standard net/http server and the autocert package for Letsencrypt.

Just for discussion would Erlang/Elixir not count as another performant implementation of green threads or would you not consider them mainstream enough?

Erlang has been scaling massively in the telecommunications industry for a very long time now even if it's not as popular as other languages.

Erlang's green threads are considered lightweight processes. They only communicate through message passing.

When selling Erlang, don't focus on "telecommunications industry" but sell based on Whatsapp: http://highscalability.com/blog/2022/1/3/designing-whatsapp....

More: https://www.erlang-solutions.com/blog/which-companies-are-us...

Green threads (gunicorn/gevent) allows you to write Python the way you always have and gain many of the benefits of async.

Uvicorn and ASGI do not. For those you need to handle async explictly.

i hear you - however the framework captures most of the abstraction entirely. In addition, most of the bottlenecks are actually i/o (db queries, etc) where its entirely worth doing it explicitly versus magic.

in a general programming language sense...ur right. But from the POV of what gunicorn/fastapi are actually used for - web frameworks - its actually quite good.