Skip to content

Comment on Things Linux Can Do That Windows Still Can't

Comments

Windows treats files as a second class citizen versus a first class like Linux / BSD. Countless time wasted because the anti-virus or some other part of Windows locked a file.

Cmder; _clink update_ ... file locked forced to wait for Windows to release it and continue working.

git pull; file locked forced to wait for Windows to release it and continue working.

git checkout; file locked forced to wait for Windows to release it and continue working.

Run an application that iterates through files, sit and wait for anti-virus to scan those files before the application / script can even touch them adding seconds or minutes to the task.

Windows can easily add 10-30 minutes of wait time after a cold boot. This is from running anti-virus, telemetry service, auto updates, ... .NET optimization service.

Windows removed the whole root user concept too. "Sorry Dave, you cannot modify that permission to remove the temporary file / change the registry value."

Microsoft even forces their bloat-ware into the IoT / embedded OS and has started to remove the ability to create a local account vs a forced Microsoft account. Windows 7 Embedded allowed full customization with removing any bloat / unused feature.

Countless time wasted because the anti-virus or some other part of Windows locked a file.

And the whole edifice of “you need to reboot to update anything” is a knock-on effect of the file locking/sharing model, leading to the misery of “we forced a reboot and lost your work again, sucks to be you”.

UNIX is the only OS that had the clever idea of advisory locking with the side effects that can bring when applications just don't care.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.