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
Wikidata is so cool, but not really public-exposed. I imagine it’s an incredible research tool though.
=> More informations about this toot | More toots from IrritableOcelot@beehaw.org
Wikifunctions finally exposed running functions via API in March, though yeah, it's still a long, long way from being integrated in wikis, not to mention the arcane parameter that is passing a JSON via URL. (and hopefully you meant Wikifunctions and not Wikidata lol)
=> More informations about this toot | More toots from Aatube@kbin.melroy.org
Oh I understood wikifunctions primarily as a way to operate on wikidata data, I don’t know if that’s right. And you’re right it is publically available, I guess I meant more that few few folks know about it.
=> More informations about this toot | More toots from IrritableOcelot@beehaw.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
since it’s JIT, it’s actually faster than Python and Java in most cases.
Java is JIT’d too, and Python can be depending on which runtime you deploy.
=> More informations about this toot | More toots from 4z01235@lemmy.world
True, I didn’t structure my sentence correctly.
It gets to compete with Java and Python because it’s also JIT is what I meant to say.
=> More informations about this toot | More toots from isVeryLoud@lemmy.ca
Node.js is a runtime, you can compile a number of languages to it. It’s useful because it can have relatively low resource usage and there are a lot of libraries available for it.
=> More informations about this toot | More toots from yogthos@lemmy.ml This content has been proxied by September (ba2dc).Proxy Information
text/gemini