Also WASM can’t directly manipulate the DOM so it can’t really be used for handling HTML/CSS, all front-end stuff still has to be done with JS.

Right now. WASM has been supported by every browser for a while now, and most webapps are made with WASM. That said, it’s not a replacement for Javascript, most people only use it on things that need to be high performance like heavier apps and web games. Nobody really makes websites that rely on WebAssembly instead of JS to my knowledge.

You can backflip in mid-air which is useful to go a little higher or cancel the direction you’re moving in. I don’t remember the exact control for it, but I think it was double tapping after jumping.

Absolutely, it’s a great game.

The fun part of this game is hearing such differing opinions, I had someone explain that Block Koala was their favorite. I personally didn’t gel with Planet Zoldath, it’s conceptually neat but I found it very tedious. Glad you enjoy it though!

The whole project just sounds weird. Any mini-PC can be used for emulation, so I’m not sure what would make this one any different. Fitting a Ryzen 7 7840 in it is also a bit overkill unless you’re planning to emulate PS3/Switch. I would expect a small PC for emulation to be way cheaper, maybe in the $200-300 range.

They explain their reasoning here: https://godotengine.org/article/about-official-console-ports/ .

I’ll post it on Lemmy once it’s done. I’m still not entirely sure which gaming communities would be most suitable but it’ll definitely be in !blogging@programming.dev :)

That said, UFO 50 is truly massive, so it’ll be some time before I finish this thing. One of the games I haven’t started yet is apparently a 20+ hour JRPG, so that’ll be fun.

I have been obsessed with this game since it came out. I’ve already put in 60 hours and got 14 games cherried (which means 100%ing them, getting a true ending, or beating a difficult challenge).

I’m writing an incredibly long blog post where I review every single game in the pack. Excited to finish & share it once I’m done playing through everything.

I remember so much pessimism last year that people’s complaints will change nothing and that almost every Unity dev is too deep and won’t be able to switch engines.

Well, guess what, so many people did switch and Unity did feel the hurt. The community really did take action.

Everyone’s going to (rightfully) dunk on Unity but I think this is a great move and it’s nice that the engine isn’t going away. Competition is always good, and I’m happy for the devs that did stick with the engine. Lots of studios celebrating on social media with a sigh of relief. I still think Godot is going to eat Unity’s lunch the next few years so they better step it up.

A bit late, but I really like it :)

It’s simple and well laid-out, and I do like the sidebar to quickly jump from post to post.

This was pretty fun! I got 3x scale and a score of 412.

Very good stuff in this update! The new page quickly showing all the changes is also a lot easier to digest than a 5,000 word essay blog post.

I’ve already been on 4.3 since the dev previews, so more than anything I’m excited for this release so the team can finally get to merging all those PRs that were shelved for 4.4. Lots of performance optimizations and big changes I’m excited for are coming in that next update. The wait continues!

Their release page has a rundown of everything new

inexperienced big brain developer see nested loop and often say “O(n^2)? Not on my watch!”

complexity demon spirit smile

This hits too close to home.

Finally, audio cackling in web builds should be fixed!

I’ve been on Nobara for almost a year now and am really happy with it. The only distro I’d probably switch to is Bazzite just to try out immutability, but aside from that I’m good where I am.

you can use OS.execute() to run console commands and run other binaries, but if you need something more advanced you can probably use C# instead of GDScript, which wouldn’t need GDExtension.

Compiling to bash seems awesome, but on the other hand I don’t think anyone other than the person who wrote it in amber will run a bash file that looks like machine-generated gibberish on their machine.

Based on the feedback we received at the GDC from partners and friends, we know that we need a way to reduce the size of our exports. Currently, the 4.3 release Web build .wasm is around 40 MB uncompressed, and 5 MB compressed with Brotli. We have a few ideas in mind to address this, and it could even help optimize builds for other platforms!

This is very exciting! It’s my #1 issue by far with the engine. With custom export templates I managed to keep it around ~25MB uncompressed, but there’s definitely a lot of room for improvement in binary size.