False. He sees grift opportunities nobody else can.

But yeah, he's not the founder.

Have you ever tried installing a Windows game manually with Wine? You need to create a wine prefix, install dependencies (msvc runtime, dotnet, fonts, etc) and maybe create a launcher script. Lutris helps you do this all through a UI.

It's not the only tool, and Steam does the same now by allowing you to add non-Steam games to your library and configure them to use Proton. But Lutris has been around longer than that feature, and it's fully open source and independent. It also has a library of community scripts which automatically apply game-specific tweaks to work around known issues.

I had a realization recently. All the pro-AI people pushing vibe coding or "coding assistants" are completely missing the point.

These tools aren't helping you write code, you are helping the tool write code, because it can't do it on its own yet. The more they improve, the less you're needed.

Idk if they'll ever reach the point where you can actually give it a prompt, and it'll provide a fully functional implementation on its own with no human intervention required. If it does, I can't imagine that tech would be as available as it is now. Your peasant ass isn't going to be vibing the next big thing that's for sure.

Look into "Oh My Zsh" or similar plugin managers. OMZ is bloated as fuuuck and you'll probably want to replace it with your own custom configs at some point, but it's the easiest way to see what a decked out zsh feels like. It's a good starting point for sure.

Personally I'm down to just 4 plugins with minor config tweaks on top of a bare zsh install. I've read good things about Starship but I'm happy with my current setup.

Reminds me of this: 2022 - Non-Euclidean Doom: what happens to a game when pi is not 3.14159…

gotem

You dont need to yse the terminal/command line for this. Just open the settings app and look for the Bluetooth section. Pairing your keyboard is pretty much the same process as on a phone ir tablet.

Btw, Bazzite has different versions. Which did you install?

TIL about bat! Looks awesome!

Using 'raw' JS/CSS/HTML is a coveted skill. A lot of people forgot and/or never learned how to do that. Those over engineered frameworks are essentially a form of premature optimization, and in many cases obsolete because modern browsers already implement their whole reason for existing.

You can, and should do that. Here's what that looks like: toolbox run -c <toolbox-name> <command>

All of my development tools are in a toolbox, including my IDE (Sublime Text). I created a standard .desktop file so that I can launch it like any other application, and it works perfectly, with a proper Icon and everything. Example:

[Desktop Entry]
Version=1.0
Type=Application
Name=Sublime Text
GenericName=Text Editor
Comment=Sophisticated text editor for code, markup and prose
Exec=/usr/bin/toolbox run -c devel /opt/sublime_text/sublime_text %F
Terminal=false
MimeType=text/plain;
Icon=/home/user/.local/share/applications/SublimeText.png
Categories=TextEditor;Development;
StartupNotify=true
StartupWMClass=sublime_text

To run something on the host from inside a toolbox, you can use flatpak-spawn:

$ toolbox enter ...
$ flatpak-spawn --host <command> <args>

You can even use that to (awkwardly) run something in another toolbox using the same command above:

flatpak-spawn --host toolbox run -c <other-container> <command>

Sublime text specifically has support for custom build commands. Sometimes, I'm using it to develop something in a different toolbox than the one sublime is installed in. So in my custom build script for the project, I add a check to enter the correct toolbox before executing the build. Here's what that looks like:

TARGET_TOOLBOX=example
source /run/.containerenv
if [ "$name" != "${TARGET_TOOLBOX}" ]; then
	echo "SWITCHING CONTAINER $0 $@";
	flatpak-spawn --host toolbox run --container ${TARGET_TOOLBOX} /usr/bin/env zsh -c "$0 $@";
	exit 0;
fi

#proceed with build...

This container/toolbox workflow is far superior to anything else, as it makes it trivial to quickly test whether your code works on a different distros/versions. It all just works with your existing tooling/local workflows once you learn how to work with the tools. There really is nothing you can't do.

...and that's for development, which is the most difficult scenario for this type of thing. For regular every day users, immutability just works without requiring people to learn anything new besides reaching for flatpak instead of apt/dnf/pacman/etc.

Just another game engine 🤷

lmao this is a targeted campaign to fuck with you. Look at people in your circle of family/friends/acquaintances/enemies and you'll find your suspect. Real viruses don't do anything as remotely entertaining as this, they just steal your passwords/crypto/etc, ransomware your files, or turn your PC into a botnet for internet spam or mining.

Download a fresh install of debian, flash it onto a usb, and do a reinstall. Use different root/user passwords that you're certain nobody knows, and ensure you lock the computer whenever you step away. Also, obviously, be careful with what software you're installing.