Hacker News new | past | comments | ask | show | jobs | submit login

Because it uses Node.js in the backend. MediaWiki is written in PHP, but it does not require you to have PHP running in the client to work.

As much as we could argue about whether no-js support really matters or not in 2020, the fact remains that having to having to load Vue.js and have it parse and render the frontend on the client is not really "lightweight", especially when the most popular competing products pre-render on the backend.

It wouldn't honestly be that much of an issue if it was a SPA (and it must do SPA-ish things already if it uses Apollo) so you just load the frontend once and it'd load other pages asynchronously, but nope. Every link is a full page reload, with Vue having to re-do everything every time.

It just reeks of modern tech used in an old fashioned way, which ends up with the performance penalties from both.

Go browse any other wiki, see how much faster and smoother the experience is.




well sometimes not being a spa and using vuejs/"any spa tech" might be a good idea. if it would be scoped correctly. sometimes you need MORE interaction on a specific page. unfortunatly the whole wiki feels sluggish as you already said, because they make so much dumb stuff.

I would say using js without having a no-js version is ok, if done correctly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: