A peek into a possible future of Python in the browser

Re:A peek into a possible future of Python in the browser by zahlman on Tuesday February 25, 2025 @04:24PM (#43177627)

>i was thinking some weeks ago that it may be time to "fork" python - as language - in a way to preserve the initial simplicity and clarity it did have and is losing faster and faster.

I've had this thought, and seen others express it. The main problem is there is no general agreement on what should or shouldn't make the cut.

I've sort-of designed a new language from scratch, but I haven't been able to convince myself to make time to implement anything significant, or even really discuss what I've already figured out in any detail.

I do like Mr. Langa's idea about pre-computed ("@blue") code - although it doesn't strike me as particularly novel. (It's something I want to do in my own language, too - or rather, I have in mind a metaprogramming system, so you'd have macros that manipulate the AST and either insert a result when it's fully determined at compile time, or runtime code otherwise.)

[ Parent | on HN ]

Re:A peek into a possible future of Python in the browser by svilen_dobrev on Tuesday February 25, 2025 @04:41PM (#43177848)

Actually i don't have that much of a problem with the language itself - the new additions are not mandatory nor breaking old stuff, by design. But the way some are used - and started to be applied and forced-down-throat regardless of usecase - leaves me wanting those features to be absent. Better not have gold at all than turn everything into gold - it's not edible.. (here mostly talking about the type-hinting frenzy. But, no point repeating myself)

[ Parent | on HN ]