Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

Agree, they really did their homework, listed edge cases, made practical compromises, chose not to overdo it, reworked it again and again quite a bit and compared it to real life experience.

It's really beautiful work, especially since touching the back bone (the import system) of a language as popular as Python with such a diverse community is super dangerous surgery.

I'm impressed.


Async was a soft keyword for many, many years in order to maintain compat. And before that, asyncio used yield to be even more compatible.

They took a decade to solidify that. At some point, you have to balance evolution and stability. For a language as popular as Python, you can not break the world every week, but you can't stay put for 5 years.


They thought about backward compatibility, and offer an alternative syntax that use no keyword for library that want to activate it yet stay compact with old version. It's already in the spec.


Especially since it is opt in, with various level of granularity, and a global off switch. Very well constructed spec given the constraints.


We heard that about types, the walrus, asyncio, dataclasses and so much more. But it didn't happen, if people don't need something (and many don't know it exists or what it does), it's unlikely they use it.

In fact, half of the community basically uses only a modernized set of python 2.4 features and that's one of the beauties of the language. You don't need a lot to be productive, and if you want more, you can optionally reach for it.

It has worked very well for the last 2 decades and it will likely work again.


People said the same about Perl and its “there’s more than one way to do things” ethos, which gained much criticism.

Same is true for C++.

In this specific case, I think a lazy load directive isn’t a bad addition. But one does need to be careful about adding new language features just because you have an active community.


Perhaps people won't use it. But I for one want it to be used, and I will certainly be using it in my own code if the PEP is accepted. Startup time is very important to me, more important than the cost of making the code noisier. I just wish I didn't have to make that tradeoff in the first place.


What if they leave?

Their company already don't produce much in France, it's all imported. They are paying minimal taxes already on what they produce and sell outside of France. And they don't pay taxes personally. So what would we lose if they leave?

For the things that are actually made in France, it's because they have to. They would have moved it already otherwise. So it's physical assets and people that can't be moved or sourced elsewhere. So what they have to produce there, they will still do. Their real estate, their logistic chain vehicles, and their local workshops will stay here. Even if they would sell part of it in fact, the actual physical stuff would stay here.

And what they sell here, they will still do: they are not going to exit the French market just because they can't be physically here so it's not going to affect the economy that much. What, less jet and luxury hotels revenue? It's ok.

And of course, we can increase taxes on their companies so that they get less revenue to compensate for their exile. We tax trading or exporting French-based company stocks so that they can't move that around without paying first.

Besides, once a stock is bought from the IPO, moving it from hand to hand is not investing more money into the company in any way. It's not going back into the economy.

They can move with their bank accounts and bonds, why do we care? It's not something that goes into our economy. They made sure of it.


Ideally, something that we could share between JS and Python.


Yes, you are old.

I meet an unexpected number of young devs that:

- Find hypermedia to be exotic. JSON web API is the only way that makes sense to them.

- Say they use the cloud to "save money".

- Use third-party services for things as basic as authentication because "it's hard".

- Encode security stuff in the frontend code.

It's the cycle of life.


Damn... looks like my job is secured for another 25 years.


Basically, ergonomic testing, but for your doc instead of your software.


No but him and his crowd have been keen on denying reality on a daily basis, and it's scary how well it works. I have people around me who drink this BS, and will argue in support for it because the arguments against it requires nuance thinking. At least, with a paper, it's harder to do this. You have to admit he pretended the sky was red, when it's obviously blue. There is less nuances if you get something clear in writing.

It's not much, but it's better than the alternative.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: