3 ms·
I think at this point Python really needs to just settle down. I don't like this not because it's an intrinsically bad idea, but adding another thing to the alr
by jerf 2y ago
I think at this point Python really needs to just settle down. I don't like this not because it's an intrinsically bad idea, but adding another thing to the already fairly large pile of things a Python user needs to know in order to read somebody else's code needs to be something that brings more benefits to the table than just "it slightly improves a particular type of function call".
At the risk of riling some people up, this smells like Perl. Some poor Python user comes across
greet"Hello {user}"
and there isn't even so much as a symbol they can search for on the internet, just an identifier smashed into a string.
But I guess Python and I parted ways on this matter quite a while ago. I like to joke about Katamari Dama-C++ but Python is starting to give it a run for its money. C++ is still in the lead, but Python is arguably sustainably moving more quickly on the "add more features" front.
- Waterluvian 2y agoMy guess at the challenge is that the community who maintain and develop a language are by that very nature not in touch with what the complexity feels like for the average user. Also it’s harder to do nothing than something. That being said, I think this is partly abstract. I’ve just ignored a lot of new Python features without issue. And while I worried that they’d force me to learn new things to understand others’ code, that’s not really materialized.
- deleted 2y ago[deleted]
- JimDabell 2y ago> there isn't even so much as a symbol they can search for on the internet, just an identifier smashed into a string. That identifier has to come from somewhere. In order for this to work: greet"Hello {user}" …they would have to first write something like: from some_tag_strings_library import greet Also, in most IDEs, cmd-clicking on `greet` or similar would take them to its definition.