cm0002@lemmy.world to Programmer Humor@programming.dev · 15 hours agoSpecifying file pathslemmy.mlimagemessage-square72fedilinkarrow-up1944arrow-down17cross-posted to: linuxmemes@lemmy.world
arrow-up1937arrow-down1imageSpecifying file pathslemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 15 hours agomessage-square72fedilinkcross-posted to: linuxmemes@lemmy.world
minus-squareHakFoo@lemmy.sdf.orglinkfedilinkarrow-up17·14 hours agoI understand pre-OS X Macintoshes used colons.
minus-squarePNW_Doug@lemmy.worldlinkfedilinkarrow-up19·14 hours 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·13 hours agoCode in Rust and you can get double colons for your library path imports!
minus-squareazi@mander.xyzlinkfedilinkarrow-up3·edit-213 hours 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