I hate that so many are trying to normalize the “release” date with the Early Access. Like no, your game being in beta testing is not “released”. CohhCarnage is doing it with his game he’s a part of, using the word “release” when he’s talking about “Early Access”. You opened up early access. Your game releases later.

It actually affected Windows 11 too

https://learn.microsoft.com/en-us/troubleshoot/windows-client/setup-upgrade-and-drivers/sysprep-as-system-windows-11

They should go back to typing code.

Want to see a neat trick? I know for sure this will work on VMware if anybody has it. Use packer to make a custom Windows server 2025 template, make sure to patch it too. Deploy said template. Now watch as you have no GUI. They updated a bunch of UI components, swapping out for ‘modern’ versions. And someone about these Appx versions get fucked when sysprep runs. It’s been like this for months.

I have no idea if this works on other platforms.

This is the type of stuff I love to see the most when it comes to PCs. This to me is far more impressive then someone with a standard case, with standard RGB fans, standard AIO RGB cooler…

This reminds me of stuff I did in college.

The uniget is a front end for multiple package managers, with a GUI front. But Chocolatey is still a separate thing, same with winget. But the GUI gives you an easier front for using those package managers without remembering commands.

When it comes to WingetUI vs UniGet… I had to look that up. My guess is WingetUI is abandoned. And was a fork of UniGet

This repo hasn’t been touched in 3 years https://github.com/rumplin/WingetUI This website https://winget-ui.org/index.html#faq I have no idea if it’s the official one, but it doesn’t link to the open source project it says that backs it. Which is sketchy. So UniGet seems to be the actual official project that’s moving forward.

My guess is UniGet is a bigger project, supporting multiple package managers for multiple OS (supports Windows/Mac/Linux).

Winget is an official tool. Chocolately and uniget are 3rd party

Game dev isn’t bad to get into. Working for those companies is the problem. It’s why we see the rise of small studios and independent projects.

Today, I ran into a bug. We’re being encouraged to use AI more so I asked copilot why it failed. I asked without really looking at the code. I tried multiple times and all AI could say was ‘yep it shouldn’t do that’ but didn’t tell me why. So, gave up on copilot and looked at the code. It took me less than a minute to find the problem.

It was a switch statement and the case statement had (not real values) what basically reads as ’ variable’ == ‘caseA’ or ‘caseB’. Which will return true… Which is the bug. Like I’m stripping a bunch of stuff away but co-pilot couldn’t figure out that the case statement was bad.

AI is quickly becoming the biggest red flag. Fast slop, is still slop.