3 ms·
Your example got me thinking about the difference between how the windows shell and Unix shell is designed. Seems like the windows shell knows about extensions,
by meken 2y ago
Your example got me thinking about the difference between how the windows shell and Unix shell is designed. Seems like the windows shell knows about extensions, whereas the Unix shell does not
That’s an interesting feature for a shell to have. Thanks!
- MadnessASAP 2y agoIt's can be traced back to the roots of each OS. Windows has it's heritage in the land of DOS where files had an 8 character name with a 3 character extension and that extension carried meaning for the OS. Linux being of Unix ancestry which had no such concept as a file extension. It was the responsibility of the application or kernel to discern what type a file was. Typically by the first few bytes of a file and handle it appropriately. I personally am a fan of the Unix way but I can see why some might prefer the DOS convention.
- D-Coder 2y agoSpeaking of heritage... 8+3 goes back at least to DECSystem-10 on PDP-10s.
- vincent-manis 2y ago6+3 on DEC TOPS-10.
- MadnessASAP 2y agoEverything goes back to the PDP-10 we are all using the incestuous off-spring of DEC. Whether that is good or bad is left as an exercise to the reader.
- NikkiA 2y agoA lot of it came from RSX11 features that got rolled into the PDP-10 OSes.
- card_zero 2y ago[flagged]