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!
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.
There are two good options: Host your own blog yourself, or join a blogging platform that isn't corporate. I personally use BearBlog but I've heard good things about Write.as as well. These two have free blogging options and don't sell your data. If you want to host it yourself (which is safer), check out Hugo.
Ultimately, bots scrape the entire internet and there's no guarantee they will honor robots.txt of a particular website (which tells bots what they are and aren't allowed to do). If it's on the internet, people can scrape your content and there isn't much you can do about it. That shouldn't stop you from writing or blogging, just don't post very personal data.
Also, feel free to join us on !blogging@programming.dev!
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.
Most variables have setters for situations like this. Rather than using get_tree().paused = false, try get_tree.set_pause(false). There's also Input.set_mouse_mode(), you'll see them under the variable names in the docs.
"Merge pull request #8 from [branch name]"
Not the most exciting but hey, someone has to do it.
It's also a lot easier to manage via code since you could just get children and have each layer have its own group.
Why? Automod is just a tool, the issues people have with it is how overzealous the mods using it are. If you're moderating a community with 10,000+ people you can't expect to filter and manage everything yourself, so a bot scheduling posts and filtering potential spam/low effort content is necessary.