News for hackers. Stuff that matters.
Re:Our Plan for Python 3.13 by coldtea on Thursday June 15, 2023 @11:17AM (#36341734)
>My point of view is that anyone who wants to write multithreaded code, shouldn't be trusted to. Making it easier for people to justify this kind of footgun is a problem.

It's 2023 already. 1988 called.

Re:Our Plan for Python 3.13 by btilly on Thursday June 15, 2023 @11:39AM (#36342081)
Did you know that Coverity actively REMOVED checks for concurrency bugs?

It turns out that when the programmer doesn't understand what the tool says, managers believe the programmer and throw out the tool. Coverity was finding itself in situations where they were finding real bugs, and being punished for it by losing the sale. So they removed the checks for those bugs.

I'll revisit my opinion of multithreaded code when things like that stop happening. In the meantime there are models of how to run code on multiple threads that work well enough with different primitives. See Erlang, Go, and Rust for three of them. Also, if you squint sideways, microservices. (Though most people set up microservices in a way that makes debugging problematic. Topic for another day.)

Re:Our Plan for Python 3.13 by biorach on Thursday June 15, 2023 @01:11PM (#36343637)
> Did you know that Coverity actively REMOVED checks for concurrency bugs?

Source?

Re:Our Plan for Python 3.13 by btilly on Thursday June 15, 2023 @01:20PM (#36343753)
Re:Our Plan for Python 3.13 by yjftsjthsd-h on Thursday June 15, 2023 @02:07PM (#36344373)
Specifically, on the last page of that:

> As an example, for many years we gave up on checkers that flagged concurrency errors; while finding such errors was not too difficult, explaining them to many users was.

(And thanks; I was also wondering about that)

Re:Our Plan for Python 3.13 by yjftsjthsd-h on Thursday June 15, 2023 @11:56AM (#36342367)
This is very witty and all, but what does it mean?
Re:Our Plan for Python 3.13 by DonHopkins on Thursday June 15, 2023 @01:45PM (#36344090)
I think he was subtly Rick Rolling you.

https://en.wikipedia.org/wiki/Never_Gonna_Give_You_Up

On 12 March 1988, "Never Gonna Give You Up" reached number one in the American Billboard Hot 100 chart after having been played by resident DJ, Larry Levan, at the Paradise Garage in 1987. The single topped the charts in 25 countries worldwide.

Re:Our Plan for Python 3.13 by coldtea on Thursday June 15, 2023 @02:51PM (#36344959)
Actually it just meant that this is a tired old argument when C/C++ programmers were new to multithreaded code.

Now we have languages and language facilities (consider Rust, Haskell, and others) to make it much safer. Same with green threads and what Go and now Java does.

Re:Our Plan for Python 3.13 by btilly on Thursday June 15, 2023 @07:56PM (#36348821)
And yet, the actual proposals for how to do multithreading in Python are essentially the same as the old C/C++ approaches. And since that hasn't changed, there is no reason to expect better results.