windows user: haha lol linux nerds gotta use the command line for everything
also windows user, on new control panel > network settings > old control panel > adapter settings > right click on interface > properties > drivers > ipv4 > properties to set a static IP address: this is okay, actually
literally this happened at the competition thing
my teammate, plugging in a device usb interface to their laptop and digging through properties in device manager to figure out what kind of stuff it exposes, takes a good minute
me: l s u s b
me, a worthless foss user with worthless opinions: systemctl suspend
you, an absolute intellectual: rundll32.exe powrprof.dll,SetSuspendState 0,1,0
the only time my laptop has ever actually kernel panicked on linux is when i was trying to test kexec and cheesed it
windows just crashes randomly, everywhere
@haskal this kind of stuff makes me miss the Amiga.
Actually scratch that, lots of stuff makes me miss the Amiga.
@haskal huh... I just assumed everyone would just have their DHCP server assign the same IP based on the MAC address.
@haskal Unless you are constantly changing static IP's... which seems to defeat the purpose of having a static IP.
@haskal Well if its not working That'd be the first thing I'd fix. But then again I'm only ever on my home network.
@haskal GUI has its merits, in case you're exploring something for the first time, or you are doing a one-off task. It's a tool for the novice and for non-repeated actions. Keeping using it for repeated (reproducible!) tasks is madness. Pushing even the power user to do so (for lack of decent CLI culture and tools) is mind-numbing crime. The solution: *every GUI* should be just a wrapper to CLI commands, that should be revealed (as part of the GUI itself), jupyter-notebook-style.
@haskal I feel like the intersection set of people who laugh at command-line users and people who set static IPs is exceptionally small.