How about a filesystem where you can't name any file con.foo or aux.bar (Windows 10), or one that silently mangles unicode into a different byte representation (Mac OS 10)?
POSIX retardation
Jonathan Barnes
Cameron Parker
Unix sucked all the air out of the room, suffocated all the competition. Nothing could compete with free and shitty but technically works most of the time.
I mean for fucks sake, just look at how many post-C languages gave themselves terrible C-inspired syntax for no reason other than C was popular and they wanted to go with the flow.
Jose Nguyen
Just trying to imagine what technical justification might exist for such an arbitrary limitation sends shivers down my spine.
Brayden Myers
C syntax is fucking brilliant.
Blake Wood
The file extension doesn't matter. It's just con and aux. And it's because Windows itself doesn't want you naming files after device nodes (CON and AUX)
Easton King
Although I do prefer Go syntax, excluding the braces on one-line if statements
Ryan Robinson
Also it is possible to force the creation of these files and nothing happens so it's probably just for some bullshit legacy or security reasons
Adrian Wood
Watch. I'm betting he comes back with Windows.
Jason Butler
It's moronic, and the gross inadequacy and ugliness of the C preprocessor proves it. It only becomes even worse when you try to use it in languages with more complex grammars. Just look at C++. Absolute trash.
Noah Ward
Why are they trying to prevent that?