WikiLambda, backend for Wikifunctions, rewrites itself from Node.js (!!) to Rust
WikiLambda, backend for Wikifunctions, rewrites itself from... #rust #node.js #javascript #wikimedia #wiki #mediawiki #wikifunctions #abstractwikipedia #wasm
https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2024-11-01
=> More informations about this toot | More toots from Aatube@kbin.melroy.org
Node.js is really not a bad backend language, since it’s JIT, it’s actually faster than Python and Java in most cases.
Rust will definitely have the advantage of being a compiled language though.
=> More informations about this toot | More toots from isVeryLoud@lemmy.ca
Somehow, it feels horrifying to use something that high-level for the backend, especially when MediaWiki has so much PHP and the WMF has so many PHP programmers. Maybe my adolescent arse is getting old...
=> More informations about this toot | More toots from Aatube@kbin.melroy.org
Oh PHP is hands down one of the slowest languages out there. It’s just convenient because it’s easy to host, but it’s awful to use and it’s really slow.
Here, have a chart:
In this chart, Java is faster than JS, but there are cases where it’s the opposite.
github.com/niklas-heer/speed-comparison?tab=readm…
=> More informations about this toot | More toots from isVeryLoud@lemmy.ca
Calculating the digits of pi seems like a poor benchmark for comparing the performance of various languages in the context of backend web application performance. Even the GitHub readme points out the benchmark is entirely focused on floating point performance.
=> More informations about this toot | More toots from elrik@lemmy.world
Absolutely, it’s just one aspect of it, benchmarking is always narrow in scope. Some languages may be good at some things and worse at others.
=> More informations about this toot | More toots from isVeryLoud@lemmy.ca This content has been proxied by September (3851b).Proxy Information
text/gemini