Referring to "the normal people you know" is purely anecdotal evidence and can't be used to infer anything at all about "side-ideology". Perhaps you only know people that don't care about the environment?
Majority of people I know care about the environment but they would never inject a phrase like that in a quick exchange about going to wash the car 50m away is my point. In wanting to be a pure heart you missed the actual point.
Yea, of course they wouldn't inject that when going to a car wash.
If the question was: "I want to go to a cafe 50m away. Should I walk or drive?" I would hope that all of my friends would answer quite a bit more pointed than the LLMs: "Walk you lazy son of a ..., why are you even asking?".
Considering that, I'd say that most LLMs are being quite nice.
Yes, but cencorship is also politics. What happens if someone just tries to stay apolitical and "work safe" and are still cencored? Any attempt at fighting this will be categorized as "political", "difficult" or worse.
Remember when they "censored" the guy who had the gall to write "men and women are a little different" at Google. There's an object lesson here, even if you disagreed with that guy.
I think the most useful thing about faxes, security-wise, is that in their basic form they require zero digital storage of the image being sent. The only record on either side of the transmission is a piece of paper.*
Contrast that with email, which is store-and-forward by design, and now you have to put in effort to ensure both the sending and receiving email providers delete the message in a timely manner.
* obviously you can add store-and-forward behavior to either fax machine, but it's not the default.
Battlefield, Call of Duty, Apex Legends, PUBG, Rainbow 6 Siege, Fortnite, Valorant, League of Legends, Teamfight Tactics, GTA5 online (and likely gta6 online).
Personally, only TFT is a blocker for me, and you can get an inferior version working on linux, but it only takes you playing one of those games for it to be a blocker.
Games "often not working under windows" is cope linux advocates tell themselves to convince themselves there is no reason for anyone to have windows installed. Its more the exception rather than then norm, and is usually the older games where their wine setup could be used on windows for the same effect.
It's not the "can't" necessarily, it's about friction, I could get it working on linux, but then I'd probably be just fiddling with settings way longer than I do today.
Current Windows gaming experience is almost like a console, just play and forget, (if you just use your machine for that).
Another potential issue is that I have games in all the major launchers (and a GamePass subscription), and the only one that works reasonably well on Linux is Steam.
I installed Bazzite just last month, it's set-and-forget. Zero hardware / driver issues, everything autoconfigured.
Didn't even need to download steam.
Absolutely shocked me how smooth the out-of-box experience was compared to even Windows 10.
To my further surprise, I found my game library's compatibility on Bazzite was stronger than Windows 10 somehow. (Some old games like Moonbase Commander don't launch on Windows 10)
Agreed - Bazzite is the kind of set-and-forget level of quality I expect for a gaming appliance. I haven’t needed to twiddle with a single setting to get any games I’ve been playing (Stalker 2, Kingdom Come 2, Doom The Dark Ages, Arc Raiders, Helldivers, etc).
FWIW - GOG and Epic games play just fine via the Heroic app on Bazzite. I’ve only played a few games from those platforms so far - but it’s been as seamless as playing games off steam in my experience.
For me the last one was Blade and Soul, and in the end, I dropped it rather than put up with it.
Even live-service games are less of a hassle than they used to be. BDO works well, Genshin works with occasionally having to update Proton, and the new shiny Where Winds Meet worked for me from the first day (never even tried it on Windows :P)
I think in the last 6 months, I've dual-booted for pretty much these things:
* To install a new motherboard's RGB-tweak utility because it doesn't work right in OpenRGB yet. Ran it once to pick settings, then it seemed to write to NVRAM since it's been stuck that way now.
* To use ham radio programming software that was clearly written by a single hobbyist and I didn't expect to work on anything but happy-path Windows systems.
* To try a weird specialty keyboard with a nonstandard card-reader (most of them just appear as normal HID keyboards, this one was a custom USB endpoint which apparently emulated a serial device with the right software. In the end, it didn't work well in Windows either-- the software was apparently mostly Win7-and-below.
* To deal with an old scanner that the vendor provides a Linux software package for, but only as a binary .deb that didn't seem to work well on Void. (Problem solved by picking up a used scanner explicitly supported by SANE for $10 at the Goodwill)
"breaking things down into the right primitives" is the real key to programming. There are many books and web pages about algorithms, but I wish there were more searchable and browsable resources for how to approach problems through primitives.
The process of breaking a complex problem down into the right primitives requires great understanding of the original problem in the first place.
Whats blocking me during programming usually are edge cases I had no idea about. Its still hard to find good material on compilers if you are not into reading dry ass books. Thats a me problem though, I simply cant force myself to read boring factual only content (one of the reasons as to why I love beejs guides).
> The process of breaking a complex problem down into the right primitives requires great understanding of the original problem in the first place.
Yes, but with experience that just becomes a matter of recognizing problem and design patterns. When you see a parsing problem, you know that the simplest/best design pattern is just to define a Token class representing the units of the language (keywords, operators, etc), write a NextToken() function to parse characters to tokens, then write a recursive descent parser using that.
Any language may have it's own gotchas and edge cases, but knowing that recursive descent is pretty much always going to be a viable design pattern (for any language you are likely to care about), you can tackle those when you come to them.
reply