opensource software that is developed primarily to work with Gnome or KDE doesn't qualify as "exclusives"... because it is opensource to begin with

there is a ton of really cool cooperation efforts going around *between* DEs, distros, etc

they don't always agree and sometimes this leads to parallel efforts, but this isn't a blodshed cutthroat market competition like with competing closed-source software or the way Steve Balmer made MS treat Linux

sure, foss software devs are human, and can have real emotional fallouts depending on the disagreement they have with each other, but it's usually very much a debate and not a war

and source code can be repurposed, etc... Linux Mint's X-Apps is actually a nice example of cross-distro and cross-DE effort, because thoae apps are good for Gnome, Cinnamon, XFCE, ... and they are made with the explicit premise to not run only on Mint, but as many DEs as could fit the app's lean requirements

the fallout between LM and Ubuntu's Snaps is very well documwnted by Mint devs, and they don't actually impede Snaps, just ship it behind a simple lock because Ubuntu started turning "apt install xxxxx" into a way to automatically install snaps and the snap version of the app, instead of a normal repo app (eg Chromium)... locking snaps was the only way they could prevent this which for them is a shady harmful practice by Canonical... but the choice to (re)enable snaps is well documented, along with the entire reasoning

that is a strong disagreement, but a well-managed one at that

View this comment - View article - View full comments

"I'm not worried about X cybersecurity threat because I'm nobody important..."

If it's a threat that really requires physical access to exploit, you should be reasonably fine... until you loose a laptop or smartphone and can't remotely ask it to nuke all your personal files like photos, banking, memorized passwords, etc...

If it can be remotely exploited, it just doesn't matter who you are and what you do for a living... there is professional malware floating around that can systematically test every door on every machine on the internet and is automated to exploit known flaws in mostly anyone's machine... at best your computer will just help them attack some other target... at worse you get some WannaCry ransomware, for which anyone is a target, or false banking website to steal access to your money, etc.

The ods that you get hit like this are not too high, and the more exotic exploits are not always in a malware's arsenal... but it's a real issue we shouldn't dismiss lightly.

Finally, if it's a "local" access threat it means someone on the same LAN can hack you... it shouldn't be too bad, except routers are almost all untrustworthy craps. Mirai and other botnets eat them for breakfast... so basically this means barely the same as remotely exploitable.

ps: i'm currently using AMD Phenom II x4, will definitely try AMD Ryzen in the future!

View this comment - View article - View full comments

Hey Liam, this is my first time posting in GoL! :)

I've been an avid reader for a while though, frequently linking GoL articles on Steam for Linux forums, and (as this article shows) I've noticed you have a good know-how on frequent rookie linux game developer mistakes, even if not a dev yourself.

Not long ago this came up in a conversation about a botched linux release:
https://partner.steamgames.com/doc/store/application/platforms/linux [External Link]

Obviously there should be more documentation (this is what is visible for non-devs), but as a public document that newbies might stumble upon, it looks seriously outdated and incomplete...

Is this something you can contact Valve about, and maybe help them include pointers on those frequent mistakes and such?

Off the top of my head I can remember a couple things you usually mention:
- case sensitive (linux) vs case insensitive (windiws) file paths
- actually uploading linux game files to the linux entry instead of a single upload to the windows entry also containing linux files
- long-standing Unity bugs and their workarounds (eg: duplicated input)

Also, maybe you could do more articles focused on such issues and have a dedicated "game development" tag for them?

View this comment - View article - View full comments