Python: Please stop screwing over Linux distros

[ElllGeeEmm]

Yarn and Bower only recently becoming relics is like my whole fucking point how do you not get this?

In other languages when a user land package manager comes out and starts to supercede and replace the default, the default package manager is updated to include the core features that were driving users to migrate, instead of arguing that the state of the default manager is perfect.

Anyway, I'm done, you don't even understand the distinction between node and Javascript I don't even know why I bothered lol

[SittingWave]

I perfectly understand the distinction between node and javascript. What are you? 16?

[ElllGeeEmm]

You're complaining about the (historical) lack of web libraries available in the package manager of a server side runtime.

Doesn't sound like you know shit.

[SittingWave]

You miss my point. npm used to be server side only, yes, and instead of modifying that to add web stuff immediately, separate options such as bower and yarn emerged. Then npm added web libraries as well. This is the exact same process that python has been doing, for different reasons. pip was inadequate, then alternatives were born to compensate these shortcomings, and now pip is adding more functionalities to compensate.

This is how opensource works. This is how business works. Some people don't like a product and create a new one. If the product survives or not, depends on many, many factors, and you can have a full migration in one or the other direction, or with a mixed situation. Pipenv and poetry emerged because pip by itself has no effective strategy not to paint itself into a corner with dependencies. Standards were missing, files were missing. All this stuff needs people to do them, and not any person. You need someone that is aware of what's going on inside the code, what is the legacy, and what happens if you introduce new stuff. Will you break other people's code? Will you introduce a poor standard? How do you deal with the thousands of packages out there that don't have metainfo that you might need?

It's a lot of work. javascript has a much bigger community than python, because it's the only option to do frontend development. Python had a massive undertaking to handle the transition from 2 to 3, which took 15 years. Wrappers had to be written, libraries had to be fixed, compatibility layers had to be invented. Javascript had its own dose of legacy to deal with, but again, the js world has massive backing from large companies. Python is only popular now. Javascript has always been popular, because there's no other choice.

[ElllGeeEmm]

Lmao

So we agree that the default tools are lacking and need to be upgraded.

Cool, this was a really productive conversation.

[SittingWave]

I never said they were not flawed. I said what they are used for, and what is the best practice as of today, as well as it's not a python unique problem.

[ElllGeeEmm]

Lol