MatejKafka

Use Kagi, it mostly excludes spam.

If your goal is sprinting 100m, using the dog seems like a better idea then, no matter how good the researchers are in other areas.

It does provide a pretty good COM interface.

It's not really important whether the text is visible, you can just put the instructions in the middle of a long document, or use a low contrast color, or a small font size, or any other of the myriad of ways to make text hard to read.

> By the way, if you don't want a culture war, you gotta stop warring.

I find it hard to understand how could steveklabnik's comment be seen as warring.

I haven't seen data that would confirm that the Nim ARC/ORC approach is faster than manual memory management (C/Rust/Zig/...) on programs with non-trivial lifetimes (for trivial lifetimes, Nim elides RC). I'd also be somewhat surprised if it was consistently faster than GC – most languages with automatic memory management use GC over RC because RC adds significant overhead, especially in multithreaded programs.

From HN guidelines:

> Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes.

I agree that culture makes a difference, but the largest aspect of it is that the average Linux user is fairly technically proficient and would be fairly unlikely to install malware even on Windows.

As for software installation, that is true for software packaged by your distro (for Ubuntu/Debian/Fedora and others, that only includes open-source software by default), and similarly, a lot of Windows software is now available from MS Store. But even on Linux, you'll need to download software manually (e.g., Chrome is not available in default Ubuntu repos, same for Discord, Slack, Teams, VS Code, Dropbox, Spotify and other common software). Even worse, less known dev tools are quite often installed with `curl ... | sh` or equivalent, which is a strictly worse alternative to installers on Windows from a security perspective.

Then, there's the question of phishing, infected torrents, fake movie pirating sites,... Currently, most malware from these sources will target Windows (various .mp4.exe files, Excel macros,...). If Windows users migrated to Linux, malware would adapt and start targeting Linux.

Desktop Linux is currently protected by being a low value target – it has low market share, and most of its users are power users, which makes them harder to trick. The opposite is true for server and embedded Linux, and it's a frequent malware target as a result.

To answer in a more constructive way:

No mainstream desktop OS tries very hard to sandbox drivers. Some drivers on both Windows and Linux (not very familiar with Mac) can be implemented as userspace drivers, as long as the performance hit is acceptable, but for many devices (e.g., graphics drivers), you need a kernel driver to get reasonable performance.

Therefore, if your OS supports loading 3rd party binary drivers (Windows do, Linux technically does as well, but tries to make them hard to use in practice), it cannot really refuse to load kernel drivers and only allow userspace ones without breaking a lot of machines.

Even if you have a userspace driver, the device may still get DMA access to RAM. IOMMU is a thing, but due to backwards compatibility, the driver chooses whether to enable IOMMU protection for the specific device on Windows.

If you're willing to write your own microkernel and bootstrap its driver ecosystem from scratch, your claims would be reasonable. With current desktop OS architecture, not really.

As for the accompanying software, there is a good explanation in another comment of all the valid use cases it has (printer dialogs, audio interface configuration,...). LG abusing that to show ads is primarily LG's problem.

I expect that process to be mostly automated, I wouldn't expect the MS folks at the testing lab to do much (if any) manual testing, especially for a new version of a previously approved driver.

I'm not surprised that the driver got approved, especially if the previous versions already had some user UI and this update "just" added the ads. What I would hope now is for MS to either pull the updated driver or ask LG to roll the change back themselves, possibly under the thread of pulling their drivers altogether (iirc they done that with other companies in the past).

Yes, and it's still fairly easy.

Agents work well on Windows for sysadmin stuff - PowerShell gives them an easy way to interact with Registry, event log, WMI and other facilities in a structured way.

Use Pro, Home is needlessly limiting for a power user.

Read sibling comments to get answers to all your (non)questions.

Except there's plenty of proprietary software for linux, you just won't find it in default repos and have to install it manually.