News for hackers. Stuff that matters.
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by xvilka on Sunday September 27, 2020 @02:43AM (#24604707)
It became less relevant in the age of Julia language.
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by viraptor on Sunday September 27, 2020 @03:06AM (#24604829)
That's a weird claim without specifying the context. Julia doesn't run python code, so that's not it. It doesn't use python's programmers... etc.

Is it "for new code which is maths/vector heavy and not relying on any existing environment, Julia is a valid competitor to pypy"? Or is there a better qualifier?

Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by pjmlp on Sunday September 27, 2020 @04:11AM (#24605064)
On the contrary, Julia might be the kick on the Python world to finally start discussing about having something like PyPy as standard.
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by potatochup on Sunday September 27, 2020 @04:32AM (#24605131)
Eh, there are still huge legacy codebaes around that benefit from pypy, not everything is worth a rewrite
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by bunje on Sunday September 27, 2020 @11:06AM (#24607162)
Currently my greatest concern is the inability of Julia to provide stability even after they've reached 1.0. On paper 1.0 is a LTS release and still supported, but how many packages actually support it anymore? There seems to be no guidelines either, the official stance is that "we move on and drop LTS when the package developers move on."
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by ChrisRackauckas on Sunday September 27, 2020 @07:18PM (#24611043)
>but how many packages actually support it anymore?

99%? You won't get the most recent versions because a lot of packages started requiring v1.3 when the new AD and multhreading mechanisms came out, but you can still boot up the LTS and run any standard analysis that existed back when 1.0 was around, which is something like 3000+ packages. Where is your FUD coming from?

Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by deadmutex on Sunday September 27, 2020 @02:44AM (#24604719)
Do you have numbers to back this up?
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by ChrisRackauckas on Sunday September 27, 2020 @07:20AM (#24605820)
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by xvilka on Sunday September 27, 2020 @02:54AM (#24604765)
See https://lh3.github.io/2020/05/17/fast-high-level-programming...

Also I should note that Julia performance greatly improved since. Next week there should be the 1.6.0 release, which will have even better numbers.

Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by abdullahkhalids on Sunday September 27, 2020 @05:24AM (#24605356)
> I don’t see Julia a good replacement of Python. Julia has a long startup time. When you use a large package like Bio.jl, Julia may take 30 seconds to compile the code, longer than the actual running time of your scripts. You may not feel it is fast in practice. Actually in my benchmark, Julia is not really as fast as other languages, either. Probably my Julia implementations here will get most slaps. I have seen quite a few you-are-holding-the-phone-wrong type of responses from Julia supporters. Also importantly, the Julia developers do not value backward compatibility. There may be a python2-to-3 like transition in several years if they still hold their views by then. I wouldn’t take the risk.
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by BlackFingolfin on Sunday September 27, 2020 @06:01AM (#24605528)
I doubt that Julia 1.6.0 will be released next week. There were no rc (release candidates) not even an alpha or beta release.
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by xvilka on Sunday September 27, 2020 @08:33AM (#24606166)
I probably messed up something, but I meant alpha, yes.