Does this suffer from all the common problems with yaml (like the "Norway problem", but many others)?

What is the "Norway problem"?

“The Norway Problem” YAML has: when you abbreviate Norway to its ISO 3166-1 ALPHA-2 form NO, YAML will return false when parsing list of countries f.e ‘[GB, IN, NO,…]’

It's a good example of how you can overengineer a relatively simple format.

The reason is that they specify a boolean value as either "true/false" or "yes/no".

The last alternative causes problems not only for the Norwegian country code (no), but also in cases where you need to specify the actual word "yes"

You could of course end up with the same problem if you need to specify the literal "true" and "false", but by overengineering the acceptable boolean values, they increase the potential problem areas.

Claiming more common words as keywords basically. It's just not well considered. true and false are ordinary words, and it would probably be better if sometime way back someone had come up with special keywords that didn't conflict with ordinary words, but for good or bad, at least by now it's practically universal in most languages that true & false are keywords and everyone knows it. Claiming yes and no as keywords also was just thoughtless and inconsiderate (ok that was redundant), doubly so when they don't even do a new job but simply double the consumed namespace to do the same job that was already done by true & false.

Eh, it's fine if they're keywords as long as not everything is a string. If `"NO"` and `NO` are distinct types, then they're not equal and there's no Norway problem. YAML treats strings, numbers, null, and booleans as all the same type (scalars). The problem isn't keywords clashing with common words, it's not having distinct types!

There's even more options apparently :)

A Boolean represents a true/false value. Booleans are formatted as English words (“true”/“false”, “yes”/“no” or “on”/“off”) for readability and may be abbreviated as a single character “y”/“n” or “Y”/“N”.

Regexp: y|Y|yes|Yes|YES|n|N|no|No|NO|true|True|TRUE|false|False|FALSE|on|On|ON|off|Off|OFF

(https://yaml.org/type/bool.html)

To be fair, yaml has a form of inheritance, I wouldn't define it a relatively simple format

To be fair, YAML 1.2 does not suffer from the "Norway Problem", but YAML is still a rather complex format.

I use make for (among other things) transforming files; batch compression being the simplest example, so all one requires is a rule saying %.log.xz : %.log and all is well.

But if people have colons in filenames, for example for timestamps, all bets are off, and make chokes spectacularly.

And that really sucks in Windows because every absolute path contains a colon. Not that absolute paths are common in makefiles, but it's not something that should break on a major platform.

Do we know that taskfile does any better than make on this front? It isn't mentioned in the article. Sounds like taskfile is runs on raw "command line string interpolation" just like good old make.

Or just don't use spaces in filenames. It just causes trouble for no benefit.

Oh yeah, tell that to Dropbox.

Don't use dropbox. That's not even just a thing to say, reclaim your autonomy and stop using a proprietary tool.

No doubt sent from a device with fully open-source hardware stack, right?

Is it conceivable to you that steps are possible, and getting rid of dropbox is a step in a direction ? That perfect is the enemy of good ? That you can't wait to find a perfectly pure plan before starting moving ?

rather fond of leading hyphens and nonprint ascii myself

Ah yes - the user should serve the computer, not vice versa, clearly.

/s, in case it's necessary.

It's more that doing the 80% solution lets us spend time developing other things. And then we can have a bunch of other really cool stuff as long as the users are willing to work with it.

Which seems like a pretty reasonable trade-off for something that's free.

It's the user serving themselves by naming files in a way that makes them easy to handle everywhere. There is also sorting and completion to consider in commonly-traversed directories.

/Τĥιs ñåmè įß ą váĺîδ POSIX /paτĥ

In GNU make? Actually, yes:

    $ cat Makefile
    a\ file: ; echo 123 > '$@'
    $ make
    echo 123 > 'a file'
    $ cat a\ file
    123

AFAIK this does work but it’s a limited workaround. Make in general just does not support file names with spaces well.

http://savannah.gnu.org/bugs/?712

That being said… In projects I just avoid filenames with spaces in general