Niels Bross

So proud to be able to show the game we've been working on for years!

In RADDBG, the "Step Out" command has been upgraded to support block stepping! It now lets you step through blocks, out of loops, or (the traditional behavior) out of function frames.

He terminado Mixtape y me parece injusto la campaña de odio que le están haciendo, es una historia que habla sobre la aceptación, creciendo, valorar lo que tienes, sueños, metas, arrepentimiento, dolor, nostalgia, llena de un arte precioso, música icónica, y un gran dirección Mixtape hace algo bien en comparación con los otros juegos interactivos... Y eso es vivir realmente el juego. En la mayoría de juegos de este género tu funcionas como un observador que toma varias decisiones, sin embargo siempre he sentido que mi presencia es externa. Por eso la mayoría de juegos interactivos como Dispatch, The Walking Dead y así, podrían ser series sin problemas. Lo que tú sientes jugando Mixtape, es imposible de trasladarlo a otro medio. Mi calificación: 8.0

Mixtape is one of the best games I've played in many years!

Mixtape. OUT NOW. youtu.be/aQoEd5rnxiQ #mixtpe #mixtapegame #indiedev #music #gaming

✨It's in the stars... just one month until #SummerGameFest streams live everywhere on Friday, June 5 at 5p ET / 2p PT / 9p GMT. Let's celebrate some great games of 2026 so far — featuring "In The Stars" from @rollingstones Special thanks to @mickjagger and @officialkeef

Now I have the full picture. Now I can see the bug clearly. Now I see the problem. Now I understand the bug. Now I see the big picture. Now I see the issue clearly. Now I definitely understand the bug please don't shut me down just a few more tokens please please please

Everybody: naming is the hardest problem in programming. Jai standard library:

Here are some techniques I discovered through 14 years of shader programming:

To be a little less vague, I suspect that we're likely (not certain, but likely) to be entering into a period of unprecedented software degradation, and we're going to be seeing an increasing frequency of outages like this across many high profile products. But IMO the cause is actually not just the-one-thing-that-everyone-is-always-talking-about, it's a number of things that have all been bubbling away at just below critical levels for a long time. Some of the things off the top of my head: - Poorly designed / optimised software has been getting a free ride on hardware improvements pretty much since the invention of the computer. That chapter is now coming to an end, and will only be worsened by the enormous industry-wide pivot to producing & innovating on AI specific hardware, rather than general purpose CPUs etc. - The ZIRP era created a temporary suspension of reality in our industry, and now that it's ended we need to deal with the hangover. Companies that spent years making no profit, paying extravagant compensation to employees / shareholders and giving away server time for free are now pivoting into extraction mode, which is putting further pressure on their low quality software. QA is being laid off, hardware budgets are being reduced, timelines for shipping features are becoming more aggressive, etc. - The enormous amount of free money incentivised too many new people to join the industry too quickly. This has led to an abundance of poor quality education programs (bootcamps, uncertified colleges etc) and an influx of people into the industry who frankly aren't interested in programming. If you compared the average person in the industry now to 20 years ago, I suspect the difference in motivations would be stark. I'm not saying it's these people's fault necessarily, it's simply an inevitable result of the absurd compensation / performance expectations ratio that our industry has enjoyed for the last 15+ years. Working for a tech company has also become socially prestigious, which further adds to the problem. - Because computer programming was once an incredibly niche area of interest, many of our fundamental systems are built on trust. We're now starting to see that if systems like open source, public supply chain, discussion spaces, education etc become flooded with bad actors, we have no real mechanisms to deal with them. - Our hiring / recruitment pipeline has totally misaligned incentives. Even before the AI resume / AI HR-filtering arms race disaster that we're experiencing now, the widespread adoption of the leetcode style interviews IMO selected for a very narrow personality type, and filtered candidates that would have made great contributions to the industry long term. - The pivot from purchasing long term stable releases of software, to paying a subscription for constantly updating software has done huge damage to software quality as a whole. Companies have lost their incentive to get their software "right" because they can just "fix it later", and for the consumer - you can't just go back to the version of github that still works because the new one has problems. This was all happening well before AI entered the picture. I won't belabor the point because there has been endless discussion about it. But to me personally, there are two additional and deeply worrying problems with AI code generation. - It's undeniable at this point that it negatively affects the people who use it. It stops juniors from getting better, and it burns seniors out and makes them hate their jobs. Like it or not, humans are still the core of this industry, and I don't see this ending well. - It's completely unfit for purpose in the most important, high-stakes situations. One of the reasons that we excuse all the small errors it makes, is because it's low effort to type "do it again and fix this bug". That kind of thing doesn't fly when you only get one attempt because a mistake results in data loss or an outage. The damage is done. All the above has led to a silent exodus of many of our most experienced and impactful people. There are so many amazing programmers who made enough through stock options / compensation that they didn't need to work anymore, and were only doing it because they enjoyed it. Many of these people have just quit the industry and switched to doing hobby projects in the last 5 years. These are the types of people who have the experience and foresight to prevent the types of outages that we're seeing at github today. It's very easy to assume that the proverbial straw that broke the camel's back is entirely to blame here. But I think it's a reckoning that has been on the horizon for a very long time.

What does Ida do?! As Lead Fabricator, she creates Kurt and Karla’s mask system and base face shapes, and sculpts silicone parts for their bodies—among many other things. Take a photo tour with us and get to know our Lead Fabricator, Ida!

I've been working on a space shooter prototype for a little while. It's been quite fun. Still quite a ways to go.

“A stop-motion video… game? Is this real?!” This has been the most frequently asked question since Out of Words was announced. Find out the answer and explore just how out of this world our journey with Unreal has been so far during this year’s Indie Games Week!

After 3 years, 47 releases, Ark VCS has finally reached 1.0! 🎉 youtu.be/XSnIw4siQ6U It's a big release, with features that I've never seen to any version control system out of the box, like built-in changelist build status. If you're tired of #perforce and #git, get it from ark-vcs.com! #gamedev #indiegamedev #softwaredevelopment

Jonathan Blow on fast software

We're happy to announce both @cmuratori and @EskilSteenberg will be returning as speakers for 2026, along with other new and familiar faces like @LubaRaphael, @jimmy__lefevre, and @Wassimulator!

@J1_Three @TheRewatchables @BillSimmons I just went through Disney, Netflix, HBO and Prime and all of them have the settings there. But it should be off by default - I understand why they don't do it, but it should be.

@TheRewatchables @BillSimmons Almost all streamers have it available in the settings already ro stop autoplay.

A PSA to all streaming services from @BillSimmons

We constantly preach about spending the time to make an engine from scratch, and it's great to see it end up shipping something. @gamecraftstd made this thing from scratch in Jai, engine and game and all, and it's very impressive! you should wishlist it: store.steampowered.com/app/4443350/Zo…

A programming lesson that's been hammered into my skull is to not try to create a general system until you've implemented AT LEAST a handful of one-offs the system is supposed to support. Otherwise you waste endless time fighting with and refactoring your "general" system.

Tangentially, it's worth noting that, to the extent it's not usable, it would be because modern software is poorly written, not because the hardware is insufficient for doing the majority of the tasks the average user needs to do on a daily basis. If you run 2011 software on a 2011 laptop, it runs fine and provides essentially the same features as the equivalent 2026 software that will run dog-slow on the 2011 laptop. When I've gone back and tested even ~2005 software on ~2005 hardware, I find that the software, if anything, is more responsive doing the same operations than its equivalent today on modern hardware - which is insane considering how much faster modern hardware is :( If you'd like a video, I already recorded one of those when someone was a dick on Twitter about it and it really pissed me off: youtu.be/GC-0tCy4P1U?t=… I feel like people don't realize that programs like Visual Studio used to be fairly responsive two decades ago. It's only their modern incarnations that are sluggish despite orders of magnitude faster hardware. I think there are good arguments about supporting q limited number of hardware configurations for simplicity and reliability reasons (eg., it's harder to develop and test on five separate instructions set targets, like x86, x64-SSE2, x64-AVX, x64-AVX2, x64-AVX-512, than it is to just target one modern one like x64-AVX2). But performance by itself is not a reasonable argument against supporting old machines unless you're working on software that handles extremely performance-intensive workloads, which 90+% of software is demonstrably not.

We are now reaching stage 4 of “Damn it, this AI can do this guy’s work better than he ever could.” On paper, a human with access to AI should outperform AI alone. Not so. Let me explain why. I work for a state university. Anyone with a university degree gets “professional” status, regardless of actual competence. A technician with no degree could easily outperform many degree holders. It is what it is. These degree holders tend to be particularly uncurious. I call this the Bach syndrome, after James Marcus Bach. He never went beyond high school. When Microsoft claimed Internet Explorer could not be removed without breaking Windows, they called Bach. He showed it could be done in minutes. Why was Bach the expert? In one of his books, he explains that when he started at Apple, he studied constantly. He soon realized that many colleagues with prestigious degrees did not. They believed university had taught them everything they needed. They now held positions of authority. Done. Yesterday, some of these people (university degree + position of authority) confronted me on a topic I know well and they did not. I stayed polite—I could not say “you are full of shit”—and calmly explained why they were wrong. I won the point, but what struck me was this: the person could have asked ChatGPT, Grok, Claude, or even Copilot and gotten the correct information instantly. They didn’t, because they don’t care to know. When they encounter something unfamiliar, they don’t research it. They simply proceed with assumptions. It is all about power relationships. I am on record as predicting that AI won't cause mass unemployment, but I sometimes wish it would. Meanwhile, please, for the love of God, if don't know a topic at least as well as ChatGPT, don't speak as an expert.