zlacker

[return to "Understanding the bin, sbin, usr/bin, usr/sbin split (2010)"]
1. sdgdfg+h6[view] [source] 2022-05-11 07:16:08
>>taubek+(OP)
Its funny how many quirks of UNIX/C/etc go back to the severe limitations of early day computers. Which is why using modern languages like Rust and its compiler really feels like coming up for air.
◧◩
2. alecmg+Ca[view] [source] 2022-05-11 07:56:16
>>sdgdfg+h6
I think Windows is even more permeated with legacy

Off the top of my head:

Nobody questions why main drive is C:, remnant of [an] early computer having two floppy (not sure) drives on A: and B:

Or more recent - C:/Windows/System32 holds 64 bit executables; 32 bit exectuables live in C:/Windows/SysWOW64

◧◩◪
3. fer+lb[view] [source] 2022-05-11 08:01:38
>>alecmg+Ca
> Nobody questions why main drive is C:, remnant of [an] early computer having two floppy (not sure) drives on A: and B:

Recently I was trying to install some obscure driver for a device that doesn't autodetect in my Windows 10 work computer, I had to go through the old school "add device" wizard. When clicking to manually provide the driver, the dialog is exactly (or almost?) the same as the one from Windows 95, and the path defaults to... A:\! There's no floppy on this computer, there even isn't an optical drive!

◧◩◪◨
4. beowul+0d[view] [source] 2022-05-11 08:16:04
>>fer+lb
Every time I get one of those it's like falling back in time!
[go to top]