What causes the jump from 69ms to 134ms?Why are Zig and Rust so slow?
Scala chads, we won
>Rust v1.69.0 69.12>Rust v1.64.0 134.91That's actually great news.
>>102888930the c code is different from the zig code
>>102888930you forgot ATS
>>102888930That's it! I am using Nim.
>>102888997Rust stable is now at v1.82 or something. OP is posting old news.
>>102889057>Knows the current version of Rust>Can't look into the bottom left
>>102889018>Nim generates native dependency-free executables, not dependent on a virtual machine, which are small and allow easy redistribution.Nim legit sounds pretty based.
>>102888930would it kill them to use appropriately sized font?
>>102888930What a bad plot, holy fuck.
>>102889125What are you even replying to him for? It has nothing to do with what he replied to.
>>102889511>OP is posting old news>Generated over a year ago
>>102888930Why is Haskell so slow? It's clearly a autistic meme language
>>102889530What? He replied to someone who was comparing the nightly version of Rust at the time as significantly faster and he informed the person he was responding to the user that it's an old build. He is correct to point out that it's old news regardless, the date doesn't necessarily mean much anyway if you really want to dig into this, there could have been 0 builds between now and then for all we know if we don't know the build versions.
>>102889016good luck getting anyone to even successfully compile that ATS program.But yes, the eternal wait for ATS3 continues
>>102888930I don't trust the measurements of a retard who can't even space out the bars a bit more to make it legible
>>102889577>Yeah we can't expect any development in one of the most shilled and recently embraced languages in a year despite a nightly being out alreadyStop posting, please
>>102889546fast haskell is tedious and ugly to write.the benchmarked code is likely only slightly speed-oriented haskell. (Not doing flagrantly slow defaults)
>>102889592just write your own bro
>>102889621I don't get what you are even posting, the OP who created the thread is positioning the table as if it is up to date information. Do you understand what the implication of the sentence "Why are Zig and Rust so slow?" combined with the picture is? The date and build versions of the table of course reveals a problem but that has nothing to do with the fact that there was absolutely no reason for you to reply to the guy with that green text. It was completely irrelevant. Probably you should stop posting cause you clearly lack reading comprehension .
>>102889657Please stop being so retarded for fuck's sake. I was making fun of >>102888997 (You) because you, there is no one dumb enough to defend this post if he didn't post it himself, compared versions tested and versions available instead of just looking at the clearly visible date. Also regarding OP's question, you could easily interpret the mentioning of Zig and Rust to be about the jump from 69 to 134. This might come to a shock to you but sometimes people pose a question and add another question to deepen or reiterate it without completely repeating themselves. Maybe OP just wanted to make fun of those highly memed languages that are constantly advertised for their speed, hence not making fun of Go since nobody cares about its speed. If you got any further questions, go outside and never visit this site again.
>>102888930>luajit still doing ok despite being mainly a one man project in maintenance mode for 10 yearsGod damn Google needs to employ some more danes or trannies to fix v8
>>102888930Where is scratch
>>102890262between my asscheeks
>>102888930bwahahahaha even c# is faster than rustrustfags BTFO
>>102890262DNF
>>102888930lmao @ lisp fags
crystal bros.....we're faster then javascript!
>>102888930Holy shit Rust 1.69 was a major performance upgrade! Thanks for sharing OP.
>>102888930How tf is Julia doing good??As for the jump, you have to remember that C/C++ has about 50 years of autism optimising it, also since the test is known, they are probably rawdogging it with reckless code, while the others (well Rust, not sure on Zig) are going to include checks regardless until the type checking algorithm knows when to safely rawdog it
>C is still the fastestThey won, accept it.
>>1028903891ms is a margin of error.
>>102888930>2023>no SIMD
>>102889657>>102889730tests are unfair see >>102890620
>>102890645Not the topic of discussion. I was making fun of some guy saying something is old and not using time as the metric. Also I doubt that all tests are fair so we shouldn't use it as a comparison anyway. Hey updated it only once since then so he might just be busy. Also alex not saying anything about the actual speed improvement is pretty sad. Something like 'I tested zig before and after implementing SIMD, got these numbers and this is the change in percent'. All just crying about a hobby project of a random guy and adding a few apparently untested linesThe really interesting point is the reason for the jump in times.
>>102890389No shit it’s readable assembly. Only way it could improve would be via esoteric mathematical algorithms that bypass the CPU.The real trick is getting C’s speed while being a usable language beyond bit manipulation on embedded systems (C++ does it somewhat but you need shitty libraries and pray it doesn’t explode)
>>102890620ease of use of SIMD is actually pretty important these days
