It's funny that this is the first time I've seen a language explicitly condone "print debugging." It's one of those things that everyone says you're not supposed to do and then does anyway.
That might just have been a failure with the GPS -- I've had the same issue before, but the car icon was offset a bit from the highway, so it looked like I was constantly driving on the grass next to it (that must have come as a surprise to the little imps inside my phone doing the navigating).
While I agree that the criticism "you're just trying to look smart" is misguided, it's a bit ironic that his response had the implication that "if I know this thing and you don't then you should be embarrassed [because I'm smarter/better than you]."
(I think that was the source of much of the objection to the comment, and the post makes no attempt to apologize for it, even if it was unintended.)
The example they give isn't really convincing, to me. I can see the usecase for this kind of language, but for e.g. searching for a pattern on the shell that isn't just one of a few predefined special cases, it seems like it'd still be a lot easier to compose regexes on the fly.
One feature I really miss in a lot of chat clients (that this doesn't appear to have) is the ability to reply to specific messages, like in Stack Exchange chat or Telegram. It makes it a lot easier to follow several simultaneous conversations, or groups with many members.
The idea that language limits or constrains the way people think (the stronger side of the Sapir-Whorf hypothesis) is now largely discredited by the majority of linguists.
Crazy idea: what if the first letter of the domain name was used to determine the first letter of the Unicode name of the emoji to select? That way there'd be some kind of mnemonic instead of having it be purely random.
It makes me a little uncomfortable that they're using curl|bash for something as simple as "put this 10-line script somewhere in your $PATH," especially when the script involves sudo (to move into /usr/local/bin). Sure, it's easy to inspect the script and see that it's not doing anything malicious, but it makes install processes like this, where it'd be incredibly easy to, seem normal.
Personally, when I write shell commands, they tend to be write-only code, because the shell isn't really suitable for anything more complex. So it's easier to think in code than it is to add the extra step of translating to English if it's something nobody's gonna see again anyway.
The `sort' example will break past one-digit numbers without the -n flag, and the example for `uniq' isn't even accurate without sorting first (not to mention the UUOC).
Setting aside the errors, the author recommends `xdotool' for finding screen coordinates for ffmpeg, but `slop -f %g' allows you to click and drag to select a rectangle and outputs a geometry string that can be given directly to ffmpeg, which is a lot faster.
Plain text is small, and the smallest limit appears to be on the order of 2MB, which is enough to fit several NaNoWriMo novels. (And that's if you're storing them uncompressed.)
Does any other language have a similar feature?