yout2

I have one but find it frustrating to use.

The hob is big enough to fit a large pan but only heats a 10cm circle in the middle. (And I have tried it with many induction-safe pots and pans.)

Rather than physical buttons, it has touch sensors that react to moisture. So a few drops of water spilling out of the pot cause it to turn off or stop working.

I think it does that for any translation term, I guess so that people can click again to hear it pronounced very clearly.

It does the same for "pico de gallo", with comic effect. (But not "gallo pinto".)

Another example: Java and C++ got disrupted by Python and Ruby, which were considered to be much simpler to read and write, but now we are seeing more static typing, for example Python with type hints and friendlier static languages like Go/Kotlin/Swift. Perhaps mirrors the shift between text editors and IDEs.

The issue is not the size of the stdlib but rather the process for how things get in there. IMHO Python's stdlib has a number of modules of sub-standard quality and design. It would be good to have a gradual process for inclusion in the stdlib, so that different 3rd party libraries could be vetted by the community before we bake one into the language.

I agree with you that it's great to have a comprehensive stdlib but I think the process should be careful and gradual. Python's stdlib has a lot of stuff that is not really best-in-class or consistent in design. I think with today's ubiquity of package managers, we could get away with a smaller stdlib initially, and take time to validate libraries with real world usage before blessing them with official status.

I think the time is ideal for the "next Python". A new, general-purpose, beginner-friendly language focused on readability, but designed from the ground up with the techniques & features learned in the past 2 decades.

Python has added lots of features to stay current with the latest trends in programming languages, but this has come at the cost of complexity and redundancy (e.g. look at all the ways to format strings or do filesystem operations). And many of the new features such as type annotations have a compromised design due to their being added to Python late in the game. Python's "batteries included" approach of a large standard library was a great asset in the days before package managers but these days I think it would be better to start with a much leaner stdlib and add things in more stringently.

channels and dj_database_url, for example.

OK thank you for the explanation :)

Curious what you mean, more specifically? Django template language seems fine to me, but maybe I haven't used React enough to see where it is better.