the scary thing about #Plan9 is when in file formats it has stuff like:
file: refers to a file
some-special-string: does a special thing
and that just invites the problem of someone using some-special-string as a file name
pls, anyone who does #programming
do not ever do anything like this
keep your formal grammars unambiguous
if you do not, Ada Lovelace will come down from Programmer Heaven and smite you
@Shamar this isn't really a Plan 9 specific problem, but it's one of those things that mess up an otherwise nice system
It makes sense in historical context, sure, but it doesn't have to always be like this.
And not all limits make you think, some are just practical because an upper bound is often nice to have. Eg. 255 characters per file name is probably a relief for on-disk file system formats.
Like, just having a standard lightweight container format would be enough, so you don't end up writing a parser for every tool.
TSV is nice because you can write an en/decoder in an hour (at most, if your C is rusty. more like 15 minutes otherwise) and it gets you enough structure without sacrificing readability
pure S-expressions are also super easy to parse, just need like... a way to do recursion??? i think? it's been a while since I wrote one (in Lua) but that too only took like 20 m.
@Shamar because they are useful
the question is, why would tools use space as a primary field separator
@Shamar like, if you wanna give files meaningful names, you're gonna use spaces
hyphens don't cut it (they have different semantic meaning in language) and underscores are irritating to type and look ugly
I mean, you can't seriously say "but that's harder to learn" when we have just demonstrated how many problems it leads to.
If kids can learn Python in a week, programmers can bear with a teeeensy bit more syntax in their shells.
Cybrespace is an instance of Mastodon, a social network based on open web protocols and free, open-source software. It is decentralized like e-mail.