Live data from Hacker News

Python 3.15: features that didn't make the headlines

blog.changs.co.uk

221–230 of 236 posts

Re: Python 3.15: features that didn't make the headlines

#221
Absolutely serious question: is anybody actually writing code anymore? (Reviewing it, architecting it, sure -- we do that). But writing code? If NOT, then seems to me, what we want in our LLM output is CODE THAT IS TRIVIAL TO UNDERSTAND (I apologize for shouting from the rooftops.)

I'm not sure adding 'features' to Python anymore makes sense - UNLESS those features help humans understand LLM code. Part of the problem is, of course, that LLMs haven't been trained on the latest-and-greatest, so they won't output any of it (even new training events won't capture the latest very much, since there is so little of it relative to what is already out there).

But again -- do new features help HUMANS understand what the LLMs produce? If not, seems to me ... new features merely add complexity for no apparent gain. (Or am I confused about this?) THANKS for any helpful opinions.

Re: Python 3.15: features that didn't make the headlines

#223

Absolutely serious question: is anybody actually writing code anymore? (Reviewing it, architecting it, sure -- we do that). But writing code? If NOT, then seems to me, what we want in our LLM output is CODE THAT IS TRIVIAL TO UNDERSTAND (I apologize for shouting from the rooftops.) I'm not sure adding 'features' to Python anymore makes sense - UNLESS those features help humans understand LLM code. Part of the problem…

Wow, the Python folks do not want to entertain different goals for the language, it would seem. I still remain interested in whether it makes sense to add features to Python anymore, given that LLMs write all the code. Unless, as I said, such features enhance human comprehension (since we have to review the code the LLM produces).

Re: Python 3.15: features that didn't make the headlines

#224
post #167

Earlier quoted context omitted.

> lambdas having pretty wild constraints (only one line??) I will never understand why people are upset about this. You HAVE multi-line lambdas. They're called functions. Yeah, I know you want a function that's only used once to be able to be defined in-line, but tbh I've always found that syntax to be pretty ugly, especially once you're passing two functions to a single call, or have additional parameters AFTER the…

once you use any language that lets you fluently inline a multiline lambda / closure you can never use Python again without it constantly irritating you

I find programs with lots of anonymous functions to be bloody irritating so I think that's just another matter of personal preference.

Re: Python 3.15: features that didn't make the headlines

#225
post #128

I come to Python around version 1.5, painfully tired by debugging CGI scripts, created by wannabe perl-golfers. Unfortunately, I feel like Python is losing more and more of the zen that once tempted me... Lazy loading looks like a last nail in the coffin, where my love to Python was buried, although it was a long, tiresome process.

It's now being used by a lot of people because they have to rather than want to so there is a desire to ** it up and reinvent their favorite language by adding all sorts of warts. That's the price of success.

A proper revenge would be to introduce "easy mode" to Rust - where the compiler takes a huge chill pill and you get non-enforced garbage collection. :-)

Re: Python 3.15: features that didn't make the headlines

#226
post #192

Earlier quoted context omitted.

> I almost never write code directly (it's always Claude) Who, then, understands the code? If the answer is "no one really", entropy will overwhelm your codebase sooner or later. Otherwise, you need to read the code, and for that the knowledge of language is still relevant.

> If the answer is "no one really", entropy will overwhelm your codebase sooner or later. Otherwise, you need to read the code I think about this on the regular -- I know the answer is currently "you own the code, so you have to understand it", but to unlock the true productivity multiplier, in the future, the answer has to be "no one really". I think about it using the concepts from my job (academia) -- to actually…

well, no need to peer-review papers anymore then! If we're to unlock the true productivity that is...

Re: Python 3.15: features that didn't make the headlines

#228

Absolutely serious question: is anybody actually writing code anymore? (Reviewing it, architecting it, sure -- we do that). But writing code? If NOT, then seems to me, what we want in our LLM output is CODE THAT IS TRIVIAL TO UNDERSTAND (I apologize for shouting from the rooftops.) I'm not sure adding 'features' to Python anymore makes sense - UNLESS those features help humans understand LLM code. Part of the problem…

If you don't write code you won't understand what you're reviewing. Any manager discovers this - their ability to review atrophies.

Re: Python 3.15: features that didn't make the headlines

#229
post #189

I used to be obsessed about language design and now, since I almost never write code directly (it's always Claude), I completely lost interest. It feels like a total waste of time and I wonder if other feel the same. One of the consequences of the LLM tsunami might be the freezing of research and development in programming languages. Maybe we'll be stuck with J's and python forever...

Presumably you don't really enjoy programming but the mistake would be to think that everyone doesn't.

Re: Python 3.15: features that didn't make the headlines

#230
post #206
post #192

Earlier quoted context omitted.

> I almost never write code directly (it's always Claude) Who, then, understands the code? If the answer is "no one really", entropy will overwhelm your codebase sooner or later. Otherwise, you need to read the code, and for that the knowledge of language is still relevant.

I do, with different tools and most of the time at a higher level of abstraction. The same way we understood the machine code 2 years ago, even though we didn't write it directly. Just another layer, nothing more.

I don't think you can really understand assembler without writing it and since compilers are fairly deterministic and get constant attention most of us using them haven't truly had to fight with what turned out to be a compiler bug.

Whereas LLMS regularly produce shit. One can excuse them for not understanding one's turn of phrase or whatever but it amounts to the same problem in the end - you have to understand the output language a lot better than most people ever had to understand assembler.

Post reply on HN