Hacker News Reader

> Windows is way behind the curve with tiled window managers

Just use one of the third party utilities.

> it forces updates on you.

Prior to this, Microsoft received over a decade of scorn for not forcing updates for 0-days and other RCEs. RCEs in the wild on Windows make the news. RCEs in the wild for months on end are bad for the entire world.

Does no one remember the complete nightmare that was going to a relative's house and realizing they hadn't updating Windows in 1 year? From bot nets to hidden folders full of pirated files (or worse...), and an overall general expectation that all banking credentials ever entered on that machine are compromised.

Yes mandatory reboots are irritating, yes it would be nice if Microsoft hired back the armies of QA people they got rid of years ago so that the updates were more reliable, but those updates serve a real purpose.

> Does no one remember the complete nightmare that was going to a relative's house and realizing they hadn't updating Windows in 1 year?

Yes, but at the same time I ran Windows XP and Windows 7 without any updates for about 15 years combined and I can count the number of times I had to format due to malware or a virus on less than 1 hand.

I once had 280 days of uptime on Windows 7 while constantly running VMs, an entire dev environment, games, etc.. It was a really good OS for what it was.

I guess the moral of the story here is if you want to play with sharp knives you should have the option to. Power users who have been using computers for most of their lives shouldn't be put on the same playing field as your 65 year old Aunt or Uncle who still thinks AOL is the internet.

You can. Block windows update addresses in hosts or install something like Wpd or shutup10.

The other problem is not providing a stable Windows distribution where updates don't touch functionality and only fix security bugs.

Exactly. It's one thing to aggressively push necessary security fixes (though they should always be optional if the user really wants, because nothing is perfectly reliable). But Microsoft hasn't done that with Windows 10. Instead, it's been systematically bundling functionality updates in with essential ones, and some of those functionality updates are unwanted or even actively not wanted by some users.

> Does no one remember the complete nightmare that was going to a relative's house and realizing they hadn't updating Windows in 1 year? From bot nets to hidden folders full of pirated files (or worse...), and an overall general expectation that all banking credentials ever entered on that machine are compromised.

When I go to my relatives for which i have installed a version of Linux, even though they don't update it very often it is never infected with anything. No malware, no virus, nothing. Always working exactly as I left it. That's one less headache when I deal with family members.

> When I go to my relatives for which i have installed a version of Linux, even though they don't update it very often it is never infected with anything. No malware, no virus, nothing. Always working exactly as I left it.

If enough people do this for their family members, when the Linux malware comes, it will sweep like a wildfire on dry wood. A complacent attitude, being trained not to worry about updates or malware is likely setting people for a very unpleasant surprise down the road.

Potentially. But the surface attack on UNIX-like systems is not the same as on Windows anyway.

I’m not so sure. Most malware I find on friend/family windows computers is installed by the user, and Linux gives you a lot more rope... At least windows has defender. The reason Linux systems that are given to family members don’t generally get malware is because those family members lack the technical ability to successfully install any new software on the machine.

unattended-upgrades in a cron-job isn't a terrible situation, particularly if you setup livepatch so you ~never have to reboot.

Please tell me livepatch actually works such that reboots can be avoided ... Ubuntu 18.04

You have to sign up for an account with canonical but it’s free for noncommercial use; it patches the running kernel.

> I would switch to native Linux in a heartbeat if Davinci Resolve worked well on my hardware

I think this is the KEY reason why I'll probably be running windows forever.

It's not that linux doesn't offer a bunch of benefits (indeed, that's why I use WSL heavily). It's that so much GUI software only really supports Windows or Mac. Linux is less than an afterthought most of the time.

This, but even then: I also need an audio stack that (a) just works, you plug in the audio interfaces, the end, and (b) supports VST/AAX/AU plugins because fairlight without external plugins is a hard no.

> I would switch to native Linux in a heartbeat if Davinci Resolve worked well on my hardware (a video editing tool that runs on Linux)

On what kind of hardware are you right now?

An i5 4460 @ 3.2ghz, 16gb of RAM, SSD, GTX 750 from ~6 years ago. My exact hardware list is here[0].

Every time I export videos of any format with Resolve it adds weird black artifacts and audio pops to my videos. The audio pops happen in every video and it only happens in the exported video, it's fine in the timeline. I'm only dealing with 1080p 30 fps videos too. These issues happen on Windows too with Resolve where as video editing tools like Camtasia are super fast and I have no problems even after 400+ videos.

I tried so hard to switch. Spent close to an entire week trying to debug everything and couldn't resolve it (pun intended).

Besides that, the machine works really well for overall Dockerized Flask + Rails + Webpack development / ops work / recording screencast videos with OBS / video editing with Camtasia / 1080p gaming (although I have a 2560x1440 monitor) so I haven't really had a strong urge to retire this workstation and build a new one.

[0]: https://nickjanetakis.com/blog/the-tools-i-use#computer-desk...

Have you reported your issues to Resolve? ANother thing, did you try on other distros, and did you get the exact same problems?

I posted the details about what happened along with sample videos on the forums but it never got a response. Resolve doesn't offer email support for the free version and the paid version has no trial so I have no way to test if things would get fixed with the studio version.

I tested it on Debian (unstable channel at the time), but the same problem happens on Windows too. If I were to try Linux again it would involve setting up a dual boot and maybe trying Arch, or at this point Debian stable maybe (when I tried unstable it was before Buster was available).

If you need to run dev stuff in a Linux box, why do you need a performant file system for WSL when using windows directories?

WSL 2's file system is running in a VM with limitations.

I have ~200gb of files sitting on a non-SSD that contain things like videos and a bunch of other files that I don't want to put in WSL. I'd really like to be able to use tools like find, grep and friends to interact with those files.

With painfully slow access to Windows mounted drives this makes using those tools not possible in practice. No one wants to wait 15 seconds to grep through a directory where the same operation finishes in 1 second in native Linux.

This becomes a real nuisance with my backup script that rsyncs things from WSL 2's file system + Windows mounted drive onto an external drive. It takes rsync over 5 minutes (!) just to figure out what it needs to send over the wire because statting hundreds of thousands of files on a Windows mounted drive is ridiculously slow. With WSL 1 it used to take about 5 seconds to run rsync with that backup script to transfer a very small diff of files. I'm not exaggerating here either. It's literally 5 minutes vs 5 seconds and I'm sure native Linux would probably be 2-3 seconds.