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

@grainloom

Which command are you talking about?

@Shamar idk, read it in some manpage the other day, not sure which
but similar problems apply to a lot of the system, eg. how basically nothing can handle spaces in file names

(hot take, $ifs should only contain tab and newline, or better yet, there should be no$ifs)

@Shamar this isn't really a Plan 9 specific problem, but it's one of those things that mess up an otherwise nice system

@grainloom

To be honest I don't know why one could need spaces in file names.

I should probably forbid them in at kernel level

@Shamar @grainloom you can't tell me what to do

@xj9

I can.

Every programmer continuously does that to users: we restrict what you can do with computers so that you can actually do something.

For example you can't put a 0x0 byte in the middle of a file name. Or a "/" in a domain name.

You are so used to our power you can't see it anymore. And actually most programmers are unaware of it.

But the truth is that we CAN tell you what to do and what not. And that's nothing!

Software programmers dictate how people THINK!

And this was true way before Cambridge Analytica: you perceive and act on the world through the software we write.

Through software we shape your synapses.

@grainloom

@Shamar @xj9 You only can't use 0x0 because of C's limitations.
IMHO, type Path = List String (maybe NonEmptyList or something) makes more sense than using char*.

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.

@grainloom

Because of C's design.

It's not a limitation, but an explicit choice. There were alternatives, but they were explicitly discarded.

@xj9

@Shamar @xj9
So it's a chosen limitation. That doesn't change much.
Other choices might make more sense now.

QOTO: Question Others to Teach Ourselves. A STEM-oriented instance.

No hate, No censorship. Be kind, be respectful

We federate with all servers: we don't block any servers.