New v0.5.0 Update #22
Mostlime12195
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey guys! It's been a long time--three months in fact--since our last update. The severe delay is not really because I've been cooking, it's more so because of my laziness, and for that I am sorry. Despite this, I have been trying to work hard in order to provide something of value.
Our last update--v0.4.0--was more of a maintenance update than a feature update, and so is this. The truth is, I can't get much done with such a messy and outdated codebase. This update, and next couple ones, will be mostly about improving maintainability, efficiency, and modernity of the WebOsu codebase. And in fact we are significantly ahead, now, in terms of how modern our code is. WebOsu 2 is now the most up-to-date version of WebOsu you can find on the web.
What changed?
Much like our preceding update, v0.5.0 focuses on upgrading the codebase to fit modern web standards. One of the first things to tackle in that case would be to migrate our code to run on the latest libraries.
To be specific, we use PixiJS for our rendering, input, and audio. In our prior update, we managed to transition from PixiJS v5 (last update circa March 2022) to PixiJS v6 (last update circa July 2023). And in this update, we've been able to migrate another major update forward into PixiJS v7 (last update circa March 2024).
What's the difference between PixiJS v6 and v7?
PixiJS v7 was a modernisation release. It changed a LOT about how PixiJS worked and its developers needed to comply with those changes if they wanted their app to work on it. One major change was the switch from ES5 to ES6, which required a great change in our code.
But I know none of you really care much about that, what benefits might it give you?
For one, you get quite a significant performance improvement. Some benchmarks show a 20-30% improvement in FPS. Moreover, the use of more non-legacy javascript code might improve reliability on modern hardware.
Alright, but what else is in this update?
The migration to v7 wasn't all, and you might've noticed that. I've recently taken the time to review everything about the website, and I've made several changes:
How often will we see new updates?
I don't know. I am very unreliable, and I have important school work. I will always accept community contributions, but I understand if you do not care to join the effort.
Beta Was this translation helpful? Give feedback.
All reactions