The Abstract Wikipedia team is working toward a rewrite of our backend services in a different programming language, likely Rust. Node/JS has served us well, but we have run up against some [WebAssembly System Interface] limits that would be best dealt with by switching to a different ecosystem.

you are viewing a single comment's thread
view the rest of the comments

[–] Aatube@kbin.melroy.org 8 points 1 month ago (1 children)

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...

[–] isVeryLoud@lemmy.ca 5 points 1 month ago* (last edited 1 month ago) (1 children)

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, where the benchmark is calculating digits of π, Java is faster than JS, but there are cases where it's the opposite.

https://github.com/niklas-heer/speed-comparison?tab=readme-ov-file

[–] elrik@lemmy.world 9 points 1 month ago* (last edited 1 month ago) (1 children)

Calculating the digits of pi seems like a poor benchmark for comparing 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.

[–] isVeryLoud@lemmy.ca 3 points 1 month ago* (last edited 1 month ago)

Absolutely, it's just one aspect of it, benchmarks are always narrow in scope. Some languages may be good at some things and worse at others.