Alastar Gabriel (but you can call me anything). I'm an ex-professional software developer, now I make weird art and music :p I will give you bug facts unprompted


Twitch, Ko-fi, Neocities, Mastodon


We can be friends but I have to warn you, I am a little awkward and kind of hard to get ahold of :p


ENG/ๆ—ฅๆœฌ่ชž OK


website
444631.xyz/
Tumblr (I probably won't use this one much)
www.tumblr.com/444631

NireBryce
@NireBryce

it's a pithy slogan and yeah the community vibes are rancid (on windows you have gamers writing most of the blogs though). It scares a lot of people who could use it to help them. it probably made me take way longer to get back to it because for about a decade I thought I'd need to memorize more, because my experiences were pre-online resources really existing.

but.

you have more problems on Linux, sure, but they're smaller. You can resolve most of them in an hour or two as long as you have Internet, but on Windows good luck finding it or having it be an easy fix.

you need to know more at first, a lot more if you aren't familiar with command line interfaces. In exchange for far less intractable problems over the life of the machine.

And for the things that fail, you need to know less overall because they're all made of the same parts. Your skills fixing one thing means you're faster when others come up. sure, packaging is a mess often and setting up stuff outside of package managers takes more work, but mostly because you're choosing where it dumps it's files.

config flags for your apps suck, but you'd be doing similar in windows -- the reason you need to use them in the first place is windows doesn't support it in the first place, so you wouldn't have the problem there, but you also wouldn't have the software. such is the cost of absolute power.

When windows fails, parts of your system gradually just stop working until you can dedicate a weekend to learning how to fix that very specific problem.


ย