Sebastian ð“€ 

21 Followers
54 Following
124 Posts
Some kind of founder @yukigunigames - He/Him
ITCH.IOhttps://seruk.itch.io/
GITHUBhttps://seruk.github.io/

RE: https://mastodon.gamedev.place/@yukigunigames/116165759483607660

Happy we get to talk about this finally! First time porting to Switch 2 and tbh did not think we would get it to look as good as we did. I’ve been wanting to make a techy blog post about the experience and the optimizations we needed to do, so hope I can find the time.

I am once again testing in prod, don't mind me
I always test things in prod 😎
AI Slopageddon and the OSS Maintainers

AI slop is ripping up the social contract between maintainers and contributors essential to open source development. Practitioners have been repeatedly assured that AI would supercharge their communities, but so far that hasn’t been the case. Just look at what happened last month. Mitchell Hashimoto’s Ghostty implemented a zero-tolerance policy where submitting bad AI-generated code

console.log()

We use std::expected.

The Ubuntu image used by our GitHub workflow only comes with Clang 16.

Clang 16 has some sort of issue with including the <expected> header.

Tried to force -libc++ which apparently would make it work. Could not for the life of me get CMake to pass that to Clang.

Then spent like two hours trying to have the GitHub runner install and use Clang 22 instead.

Keep pushing to main to run the workflow, rip our git history.

This is not very fun 🥹

#cxx #githubactions

Recent discussion about the perils of doors in gamedev reminded me of a bug caused by a door in a game you may have heard of called "Half Life 2". Are you sitting comfortably? Then I shall begin.
@aras I visited the Unity office last year for work and I got presented some new profiler features in a meeting room bigger than the room in the photo 😅
@runevision The build configuration system you developed supporting both inheritance and partial overriding is very interesting, as that is my #1 critique of the system that Unity actually rolled out. I’ve built a package for internal use solving the same thing, and those features are critical to not end up with a pile of assets to modify that single setting you need changed between two similar SKU:s. Maybe they should’ve looked closer at your stuff!

Sunday's thread on why chatbots & LLMs are a bad solution for information access, with replies to the most common types of counterarguments I encountered in my mentions.

https://buttondown.com/maiht3k/archive/information-literacy-and-chatbots-as-search/