Is Python Fast Now??! | Python 3.13 Released

Is Python Fast Now??! | Python 3.13 Released

Cheesed Up

1 месяц назад

7,072 Просмотров

Ссылки и html тэги не поддерживаются


Комментарии:

@MrAlanCristhian
@MrAlanCristhian - 20.10.2024 19:35

The biggest drawback of mojo is the same one when python 3 came out: it's a different language. The python 2 to 3 transition should be a good reminder of why backward compatibility is important. In an interview with Lex Fiedman, Guido Said cpython incompatibility was the main reason that killed those project that tried to make python faster. And mojo is doing the same mistake. So, I don't see a bight future for mojo.

Maybe I am wrong, time will tell.

The Faster-CPython team has some great optimization ideas that (hopefully) will be implemented on 3.14. Look at 701 issue on the faster-cpython repository for a quick recap of what they are doing.

Ответить
@cckeysify
@cckeysify - 21.10.2024 00:03

i hate python its an ass language

Ответить
@tonylangworthy5479
@tonylangworthy5479 - 21.10.2024 05:21

Stop right here bro... Until Pyton syntax changes, idc how fast it is. Facts!

Ответить
@fraidoonhu9284
@fraidoonhu9284 - 21.10.2024 14:34

I don't care about speed. But Python syntax is the unforgiven mistake human beings ever made. Specially when u use lambda function.

Ответить
@k98killer
@k98killer - 22.10.2024 18:17

Snake lang has some of the nicest syntax imo. It is far easier to read and comprehend existing code than other languages that have more complex syntax (e.g. Rust Thing[Something]<T<W>>'A), which is important if you care about maintaining code bases. The main downside to Python is the low performance compared to all the other languages -- for example, when I ported my bluegenes library from Python to Go, I got a 100x speed improvement before doing any Go-specific performance tuning and memory optimization. But I still love Python and write the majority of my FOSS projects in it, so I'm kind of stuck with it for now. Hopefully they figure out a solution that removes the GIL without making the runtime twice as slow. Iirc, Guido said that the GIL was a solution for a time when single-core performance was all that mattered, and More's Law was still in effect for individual CPU cores.

Ответить
@vidal9747
@vidal9747 - 23.10.2024 05:07

Python is similar to Fortran in concept. Fortran was easy to use (much easier than Assembly, which were prevalent at the time or C, that came after a while.), so researchers and people who are not computer scientists but need to code liked it. Python, when using the right libraries, is fast enough for a lot of scientific computing. The problem is that, like Fortran, you have to pull up C when you need to do something more advanced or if Python is too slow for your purpose. Python is still a very good glue between various languages. Basically, if Python is faster, researchers in every area that isn't computer science are going to have a better time with their code. Fortran was easy to use and fast. If python becomes fast, even if it is not as fast as Fortran, it will keep being used. Julia was born with this premise.

Ответить
@Ahamshep
@Ahamshep - 23.10.2024 07:48

GIL doesn't look that tough. I could kick his ass.

Ответить
@surajmandal_567
@surajmandal_567 - 24.10.2024 07:39

Waiting for Mojo to get some more mature.

Ответить
@umcanalsemvidanoyoutube8840
@umcanalsemvidanoyoutube8840 - 24.10.2024 16:01

Lua/LuaJIT >>>>>>>

Ответить
@muslimgamerrr9479
@muslimgamerrr9479 - 13.11.2024 23:31

is this going to be a experimental feature or in the future will it be default?

Ответить
@idocoding2003
@idocoding2003 - 16.11.2024 05:57

We have mojo for speed

Ответить