cm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agoSpecifying file pathslemmy.mlimagemessage-square128fedilinkarrow-up11.38Karrow-down114cross-posted to: linuxmemes@lemmy.world
arrow-up11.37Karrow-down1imageSpecifying file pathslemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agomessage-square128fedilinkcross-posted to: linuxmemes@lemmy.world
minus-squareHakFoo@lemmy.sdf.orglinkfedilinkarrow-up17·2 days agoI understand pre-OS X Macintoshes used colons.
minus-squarePNW_Doug@lemmy.worldlinkfedilinkarrow-up20·2 days agoThey did! And I weirdly kind of miss them for the entirely non-logical reason that they looked elegant. Don’t get me wrong, I adapted in about 3 seconds when I made the switch to Mac OS X 25 years ago, but I irrationally kinda miss them just a tiny bit.
minus-squaresaplyng@lemmy.worldlinkfedilinkarrow-up8·2 days agoCode in Rust and you can get double colons for your library path imports!
minus-squareazi@mander.xyzlinkfedilinkarrow-up3·edit-22 days agoRISC OS uses periods and doesn’t have file extensions
I understand pre-OS X Macintoshes used colons.
They did! And I weirdly kind of miss them for the entirely non-logical reason that they looked elegant.
Don’t get me wrong, I adapted in about 3 seconds when I made the switch to Mac OS X 25 years ago, but I irrationally kinda miss them just a tiny bit.
Code in Rust and you can get double colons for your library path imports!
RISC OS uses periods and doesn’t have file extensions