Raymond Hettinger has a great talk about how much python's dict has improved over the years. So this is super interesting and will probably just make the builtin dict better eventually.

The lesson of the talk is that if you are idiomatic then you will benefit as the language improves.

https://www.youtube.com/watch?v=npw4s1QTmPg

Very cool presentation. I loved how he says that they improved dict so much that they basically rediscovered database tables with indices.

Dave Beazley has a great talk about using Python built ins.

Def worth a watch as he is funny but also super cool to see someone use a REPL this way:

https://www.youtube.com/watch?v=lyDLAutA88s

I always assume an app that uses an installer is hiding something from me.

In my experience, an app that doesn't use an uninstaller is giving me the gift of hunting for hidden treasure all over my hard drive.

this is just sales slop for their own product.

Yep.

If you dig through, they do have a repo, licensed under the AGPL, of course. No software, though, just markdown files.

did they, like, not lose a million jobs tho?

Duplication is fine, triplication and above is the issue.

Triplication tends to be where it becomes more clear what the correct thing to abstract or de-duplicate is.

It's of course possible to functional-ize segments of logic, but then the question of state mutation must be brought up. How isolated are these changes from other parts of the code / system state. Can this be run in parallel or is it something that must be serial? What potential race conditions exist?

me waiting for the "the rise of posts analyzing the rise of the em-dash on hacker news" posts

It'd be nice if desktop safari was a column.

damnit, I just happen to like the look of the thing. now everyone thinks I'm AI for pausing in my thoughts as I write—as if I were human...

I mean, have you looked outside lately?

because two colors of functions suuuuuuuuuuks to deal with

Doesn't really explain why async/await are hugely popular in C#, JavaScript, etc. but didn't take off in Python.

I'd explain your cases this way:

C# has a dictator with a budget: Microsoft integrated async into C# in a formal way, with 5.0, including standard libs, debugging, docs, samples, clear guidance going forward, etc. What holes there were were dealt with in an orderly and timely manner.

JavaScript actually had a pretty messy start with async, with divergent conventions and techniques. Ultimately this got smoothed out with language additions, but it wasn't all that wonderful in the early days. Also, JavaScript started from a simpler place (single-threaded event loop) that never had "fork" and threads and all that comes with those, so there was less legacy to accommodate and fewer problems to overcome.

Python had a vast base of existing non-async software chock full of blocking code, plus an incomplete and haphazard concurrency evolution. There are several legacy concurrency solutions in Python, most still in use today. Python async is still competing and conflicting with it all. Not unlike the Python 2->3 transition.