Code correctness that relies on how far one has "gravitated" in their coding style and/or whether people agree on and/or adhere to those styles is the issue. All your brace-delimited examples work the same. White-space delimited variations won't.

Yes, but it's quite possible that the code won't parse correctly w/o the braces (or with extra braces), where improperly indented Python probably will, and just execute incorrectly. I'd rather have a parse/compile error than run-time error or, more likely, improper execution with no error. Sure, examples can be made either way, but missing/extra braces *can* be detected by the parser. Missing/extra white-space, not so much.

Regardless of whether one (dis)likes white-space delimited blocking, it's main driving force is the ego of the language developer who has declared it "more elegant" than braces, even though the syntax offers absolutely no enhanced benefit.

In addition, according to the Language Manual, Nim supports the directive "#! strongSpaces" to allow white space to affect operator precedence. An example from the manual:

So with/without the directive:

• with: ((foo+4)*4 == 8)
• w/o: foo+((4 * 4) == 8)

In addition, claiming "more attention" by submitting a post containing several links to articles about the subject seems a little astroturfy. While certainly a small circle, neither I nor anyone I know has heard of this language until now, and still probably won't ever care.

In addition, this tidbit, from the Nim homepage, under "Nim is elegant" make's it a no-go for me:

As with Python, this is retarded and unnecessary.

Or a sadder, non-action-movie version, Never Let Me Go - based on the book by Kazuo Ishiguro.

Ya, you're not the first to comment on my fat-fingers - though that you (both) felt compelled to do so might say more about you two than me. :-)

Seems to work for the NSA and other three-letter agencies ...

When took LISP way back in college, the instructor asked a student what he wanted out of the class. The kid said, "an A". The instructor said, "no problem" and wrote "A" on the blackboard. Then he asked the kid his name and wrote it on the blackboard - "Steve's A". The instructor said, "I imagine you'll want to take that home with you," erased the writing and smacked the eraser down on the kid's notebook. The instructor then remarked, "notice how your grade has been encrypted and stored as a nice little bit pattern for you."

Ah, college...

I'd use a cross-cut shredder, then send it to you in a paper bag along with some Scotch tape. (You didn't specify how easy it needs to be to decrypt, especially if I include some random shredded pages in the mix.)

Works for most types of files: Excel, PDF, etc...

I store my undeadable code using a Walking Dead technique, whereby the binary code is reaped from the the return statuses of zombie processes killed at the last possible moment ...

Better crackers are going to love breaking this in 3, 2, 1 ... :-)

The officer has a computer and data uplink in his vehicle - and a radio. Do you think he's going to trust *your* phone to verify *your* license? No he's still going to run it through his system, and to check for outstanding warrants on you, etc... Having your license on your phone does nothing to speed up the process, just allows the officer to your, freely unlocked, phone.

Unless, by enormous failure, you mean, has been working for hundreds of years, then citation please. No one's stolen my driver's license or any other physical documents - ever - and they're pretty simple to use - no batteries or cell signal required. In addition, I don't have a smartphone.

You talk whitespace abuse and don't even mention Python - for shame. :-)

Okay. How do we get that punishment implemented out in the world?