5 ms·
Human friendly with curly braces? I don't buy it. I would never unleash a curly braces syntax on a non-developer. And if it's a format for developers then ther
by andybak 8y ago
Human friendly with curly braces? I don't buy it.
I would never unleash a curly braces syntax on a non-developer. And if it's a format for developers then there are already plenty of options.
- z0mbie42 8y agoHi, on of the major benefits pf adding braces is the support for auto format (think go/rust fmt). Furthermore, how would you explain to a non developer that ``` a: b: nested ``` is different than: ``` a: b: non nestee ```
- krapp 8y agoCurly braces are not that unfriendly - people use parentheses in common text all the time, and curly braces are not that different. Perhaps the concept of a "block" or scope is a bit unfriendly but that's independent of syntax... and arguably, curly braces make that more explicit. Meanwhile, with significant whitespace, non-developers have to learn to be aware that a syntactic element intended to mean nothing now suddenly means something, and that one type of whitespace means something different than another and that they can't be used together, which is counter-intuitive.
- andybak 8y agoI think semantic identation is very intuitive to non-developers. It's used in print everywhere. I think there's a touch of Stockholm syndrome in your belief otherwise. You have been corrupted and are projecting "intuitive" on to the pure. ;-)