Re:macOS deprecating scripting language runtimes, including ...
by saagarjha on Thursday June 06, 2019 @01:22AM
(#20111825)
> macOS uses '/' as a directory separator already
Depends on what level of the UI you're dealing with.
Re:macOS deprecating scripting language runtimes, including ...
by ardy42 on Thursday June 06, 2019 @01:28AM
(#20111848)
> But macOS uses '/' as a directory separator already.
IIRC, HFS actually uses a ':'.
Re:macOS deprecating scripting language runtimes, including ...
by cynwoody on Thursday June 06, 2019 @02:41AM
(#20112148)
Mac OS versions prior to OS X used ':'.
Mac OS X, initially released on 24 March 2001, uses '/', like other Unix-derived systems.
Also, like other unices, OS X uses '\n' as the line ending. Prior Mac OSs used '\r' as the line ending. Windows uses '\r\n'.
Re:macOS deprecating scripting language runtimes, including ...
by pjmlp on Thursday June 06, 2019 @07:16AM
(#20113377)
In A/UX you could use both.
Re:macOS deprecating scripting language runtimes, including ...
by hestefisk on Thursday June 06, 2019 @05:07AM
(#20112805)
Similar, HFS+ used to provide the option for case insensitivity. Both things were built in for legacy support reasons during the transition from OS 9 to X, as with Carbon.
Re:macOS deprecating scripting language runtimes, including ...
by zwily on Thursday June 06, 2019 @08:13AM
(#20113741)
Macs still come with case insensitivity on by default.
Re:macOS deprecating scripting language runtimes, including ...
by codesnik on Thursday June 06, 2019 @05:06AM
(#20112802)
but in Finder you can use "/" in filenames, and can't use ":". They got swapped if you look on the file from Terminal.
Re:macOS deprecating scripting language runtimes, including ...
by gsnedders on Friday June 07, 2019 @09:30AM
(#20124260)
Pretty sure HFS doesn't actually store any directory separator. A directory, after all, is just another file, each one containing its own children. Classic Mac OS used ":" when it needed to use something as a path separator.
Apple isn't changing things just for the sake of change. They're removing 1970's-isms where they hold back the platform. Languages like Ruby/Python/Perl also clean house, from time to time, to remove old cruft. I can't imagine any legacy feature of macOS that Apple would want to deprecate which would make it more difficult to maintain a good port of Ruby/Python/Perl. These are regular general-purpose programming languages now, not just Unix scripting languages.
Yes, Unix has been one of the developer systems of choice for the past couple decades, but it wasn't always so, and it hasn't been the only one. I hear more developers than ever using and enjoying other systems like Windows (Powershell) today. Even Linux today is pretty far from traditional Unix. I just don't see perfect Unix compatibility as a necessary component like it was in 2001.