fault1
Joined 5 years ago
Joined 5 years ago
Of course, the exact heuristics to weight authority are in a continuous flux.
What you say was bad about it? And who were the bad people specifically? The people who were using python 2 or python 3?
For what it's worth, python3 >= 3.0 && python <= 3.2 were hideously broken in their unicode support. Arguably had worse/unusable uncode relative to python 2.6 or 2.7.
So there was a huge failure to launch type of problem, especially given how long python3 had been development.
It most definitely left a very sour taste in many people's mouth that didn't start dissipating till 3.5 or 3.6 when enough "killer" features had accumulated.
Even then, for a lot of usages, python 2.7 'just works'.
Often the same thing in for example, typical wall street firms before 2008.
Many jobs are fully remotable now (tho it varies from almost all of them like Meta, to almost none of them like Apple). Sometimes slightly less money.
A friend of mine made a decent amount just tracking the tweets of Elon Musk and other coin influencers a few years ago.
Agreed. This might have been applied to the "Zen of Python" days back in 1999, when the competition was Perl, but python has slowly morphed into a more and more perl-like language.
Julia has one good library for this (JSON3.jl), but it really should be embedded in the language.
Furthermore, Julia has very nice support for multi-dimensional arrays, but it's built in support for dictionaries/hash maps isn't very good, and they might be more prevalent in many types of data processing (certainly in many "big data" types of workloads). There is another third party library for this (Dictionaries.jl) but once again, in practice, JavaScript and TypeScript not only much faster and more optimized for this, but also have better tooling available out of the box.
Again, not a knock on Julia at all, it's great for certain things, but it's important to understand where the ecosystem has gaps are and where things can be learned from other ecosystems.
How Python was Shaped by leaky Internals(2016):
https://www.youtube.com/watch?v=qCGofLIzX6g
See also this HN post (Attempts to make Python fast):