Python 3.14 is here. How fast is it?
321–330 of 579 posts
Re: Python 3.14 is here. How fast is it?
#322Re: Python 3.14 is here. How fast is it?
#323Re: Python 3.14 is here. How fast is it?
#324Re: Python 3.14 is here. How fast is it?
#325Earlier quoted context omitted.
It's two different computers with different CPUs, so different runtimes are expected and has nothing to do with the OS. > Framework laptop running Ubuntu Linux 24.04 (Intel Core i5 CPU) > Mac laptop running macOS Sequoia (M2 CPU)
Yes, and why? way to not address the question at all.
Re: Python 3.14 is here. How fast is it?
#326What about Lua and LuaJIT
Re: Python 3.14 is here. How fast is it?
#327Earlier quoted context omitted.
Given how mature emulation is now why couldn't that just continue to be possible into the future?
Each new layer of emulation is new code that needs to be written that wasn't required when the original program in question was written. It's a great approach for software preservation, but the fact that it's necessary shows why the approach of "if it ain't broke, don't fix it" doesn't work. The context of computing is changing around us at all times, and hardware has a finite lifespan.
Arguably modern operating systems are all sort of virtual machine emulators too. They emulate a virtual computer which has special instructions to open files, allocate memory, talk to the keyboard, make TCP connections, create threads and so on. This computer doesn't actually exist - its just "emulated" by the many services provided by modern operating systems. Thats why any windows program can run on any other windows computer, despite the hardware being totally different.
Re: Python 3.14 is here. How fast is it?
#328I hope it doesn't get stuck at 3.14, like TeX. https://www.reddit.com/r/RedditDayOf/comments/7we430/donald_...
You hope it doesn't ? > [Donald Knuth] firmly believes that having an unchanged system that will produce the same output now and in the future is more important than introducing new features This is such a breath of fresh air in a world where everything is considered obsolete after like 3 years. Our industry has a disease, an insatiable hunger for newness over completeness or correctness . There's no reason we can't…
Consider how vastly more accessible programming has become from 1950 until the present. Imagine if math had undergone a similar transition.
Re: Python 3.14 is here. How fast is it?
#329Very interesting post, thanks for putting it together. Rust is indeed quite fast, I thought NodeJS was much better tbh., although it's not bad. I'd be interested to learn what's holding it back because I've seen many implementations where V8 can get C++-like performance (I mean it's C++ after all). Perhaps there's a lot of overhead in creating/destroying temporary objects.