@Specialist_Being_677
It may be because I’m not a software developer. But sometimes I wonder whether it wouldn’t be helpful if there was a set of Unicode characters for code. It may make code easier to read, especially for beginners.
You would need a specialized keyboard or a clever code editor. And of course all experienced coders would probably run amok.
@parapluex
Thanks! I wasn’t aware of that. It looks like it does all I was thinking of and more. And yes, it doesn’t look more readable than other code to me.
I think that in the back of my mind I was hoping that that would make it easier to jump between programming languages but it’s just another programming language 😁
I think what I had in mind was more something like a powerline font in the shell.
When I read announcements like that my first question is always: Is the "🖕" emoji allowed?
@mndflayr @Natasha_Jay I’ve got *two* variants in my phone’s text shortcuts:
If I type qbird, it becomes ಠ︵ಠ凸
If I type qb2, it becomes ‘Hmm, where is that emoji... ah, yes... 🖕’
I keep it around as a. png on my work notebook, 'cause - of course - it is missing from our chat solution there. So I can paste it when needed.
It drove some colleagues mad, because they tried and tried to convince the chat to show that emoji.
@casandro @Natasha_Jay Except that that all too popular operating system does not have "opaque byte-strings" for paths, and instead insists that paths are not-quite-UTF-16 strings, has per-directory settings for case sensitivity (implying that any previous mention of paths being "opaque sequences of WCHARs" is a lie), may or may not do some form of Unicode normalisation, and forbids certain characters or names-before-the-extension unless you rewrite your paths. Note that that last bit also makes it so that . and .. are allowed path components, much unlike any POSIX-like system.
I'm not too surprised that Dropbox took a while to make it "just work".
@mrotteveel Chinese, Korean, Japanese all have characters outside the BMP and therefore require surrogates in UTF-16. Most notable Chinese Han characters, which are frequently used in personal and place.
Besides: NTFS and FAT both moved from UCS-2 to UTF-16 as early as Windows 2000/XP. ReFS has always been UTF-16. Linux and BSD standardized on UTF-8 around the same time. macOS/Darwin has always been UTF-8.
This issue is a vocal minority's non-issue.
@taschenorakel @GromBeestje @Natasha_Jay that escalated quickly
*puts on MAGA hat*
keep emojis out of filenames! make ASCII great again 
@Natasha_Jay who asked for this?
Let's find those people and beat them for hours with colorful Wacky Fun Noodles®.
@Natasha_Jay
AAAARRRRGH!
It's a joke, yes? Please?