timkofu

Very nice.

The JIT requires no code changes to existing projects, and immediately enables more efficient use of hardware that is becoming ever more expensive by the day.

Free threading does require code changes, and a different programming mental model.

Hopefully it's a YES, and defeat won't be snatched from the jaws of victory.

How is this different from SWEBOK? https://www.computer.org/education/bodies-of-knowledge/softw...

I used to use VyOS for this.

Nice.

I’m gaining more confidence AI is unable to take any of our jobs if this level of marketing is needed to try to convince us it will.

Exactly.

It's like saying "robots are replacing civil engineers". Asphalt laying is about 10%? of the work required in commissioning a road. The deciding whether to build a road at all, the costs, where to build it, the math all need to be done by a civil engineer.

The bulk of Software Engineering is feasibility study, requirements gathering, detailed design (architecture) then finally the implementation phase where AI comes in.

Those stages are in order of importance. Getting it wrong in especially the first two results in a high quality shiny white elephant at best.

The implementation phase is at most 20% but on average 10% of the work required to commission reliable maintainable software.

I’ve been using Django several years now. It works. Some things could be more straightforward, but once they work, they’re stable. I’ll keep an open mind though.

Thanks for this.

It would be interesting to this repeated with Starlette and Granian on Python 13 (with GIL and JIT).

Django.

Plus with Django and Py03, one can write the service layer in Rust(if you’re into that).

It also enables building an interface to Python’s data tools.

Thanks for this. I've been looking for a Django-esque web-framework for Rust for a while now, and it would seem I'm not the only one[1].

Also, if you're open to suggestions, use SemVar, and have releases on GH so we get email notifications.

[1] https://news.ycombinator.com/item?id=41760421

There has been funding in recent years to fix the quirks and improve performance. The Faster CPython project has had good outcomes towards achieving these goals.

Python 3.13 will have a JIT, and true threads. It'll likely take a couple more releases for these features to be stable and utilized throughout the stdlib and the wider ecosystem. In a few years, performance and quirks will likely not be an issue.

This should have been a microwave link from the start.

Firefox is not on the brink.

It’s evidence of division and strife. They have allowed the environment to get toxic. Groups that were planning on adopting Rust will now think twice, as it’s future now looks uncertain. All organizations that produce something valuable face this test, it’s the ones that don’t fracture that succeed.

> Lots of comments here are stating that typing is half baked in Python, and that if you gotta use types, you should use another language

... I thought this is how most of us use Python? I find it repulsive to use without types. type_hints enable me to use it for Software Engineering, and I get to keep the Data Science stack, which is solid gold.

Expected, and welcome.

Thanks for sharing this.

Possible to make the list a GitHub project that we can contribute to?

Yes.

> Python can be ahead in the performance race. We just need to get real.

Completely agree, and Instagram did it, and they have been reaping the benefits for it. Now they've open-sourced the runtime, so we can all benefit now too.

Now we’re getting somewhere.