Last time I ran a corporate-made installer, it caused massive graphical glitches and lock-ups after waking from sleep. It basically gave my system computer-AIDS.

That’s why I never run scripts which are too long for me to easily understand outside a sandbox. Official distro repositories and Flatpaks are the only sources I have some level of trust in.

Team blue for both.

Touchscreens can stay, but only for non-essential tasks like changing settings or entering addresses. Climate, media, and all other controls you usually use while driving should be tactile by mandate.

That’s bog standard KDE, I have no idea about the distro tho

People on Hacker News are speculating that they implicitly define forking as “taking the project in a different direction in an independent repo”. The Github TOS say that everyone has the right to create a fork of any public repo in the Github sense of the word. It’s all a huge mess…

They have the audacity to use the term copyleft for that bullshit license… It doesn’t mean anything unless you have the right to fork it.

I applaud your bravery with Arch. Have some fun with it and don’t worry if you break stuff. Keep your files backed up and you’re golden! Even if you switch to a different distro later on, a lot of what you learn will translate 1:1.

I tries it a couple months ago and it was horrible, didn’t even support flexbox back then and it kept crashing. The latest nightly builds are almost usable for basic web browsing though, it’s amazing how fast servo improves

The USB spec requires one master and one slave device, which is usually decided by which type of connector each side has. USB OTG can bypass that restriction, but I’ve only ever seen it done with micro USB or type C.

TIL Pulsar exists