Earlier quoted context omitted.
Only programmers from English-speaking countries like ASCII. There are millions of us living in other countries who are thankful that Unicode exists, and who are constantly annoyed that a some of our tools don't support it well enough. As someone who grew up bilingual in a country where it's not uncommon for people to speak three or more languages, I hate the idea of being prevented from using one of the languages I…
Ironically, you can't even write proper English in ASCII. It is missing many characters widely used in English text.
Gitmoji – Yay or Nay?
101–110 of 224 posts
Re: Gitmoji – Yay or Nay?
#102That's a no from me. I am not a huge fan of emoji. Especially not in the cli or editor. Emoji are hard to type on non-mobile platforms, and are difficult to search for in logs or files. Often they don't render properly. They're near impossible to deal with from the command-line. Not to mention the accessibility issues. I see no reason why these cannot be accomplished with tags/flairs such as [critical], [bug], etc. T…
> Emoji are hard to type on non-mobile platforms On Windows they are easy: + . Finding the right emoji is easier than on my Android phone as Windows lets me type the emoji name. Why emoji search is missing on Android... who knows.
Re: Gitmoji – Yay or Nay?
#103Earlier quoted context omitted.
Wait, I thought the goal of it is not to write emojis per se but rather use the shortcodes. That way, it's readable even when emojis cannot be rendered and it even makes search easier. So a typical commit message would read like that: `:bug: Fix login modal` It doesn't break anything and when interpreted (github, gitlab, gitkraken, etc...) it displays a nice looking emoji.
Doesn't 'fix' already mean there was a bug, that was 'fix'-ed?
`:lipstick: Revamp login modal`
Re: Gitmoji – Yay or Nay?
#104Re: Gitmoji – Yay or Nay?
#105That's a no from me. I am not a huge fan of emoji. Especially not in the cli or editor. Emoji are hard to type on non-mobile platforms, and are difficult to search for in logs or files. Often they don't render properly. They're near impossible to deal with from the command-line. Not to mention the accessibility issues. I see no reason why these cannot be accomplished with tags/flairs such as [critical], [bug], etc. T…
Cmd+Ctrl+Space brings up the emoji palette on MacOS. This palette is easy to use from the keyboard and works in the terminal too. Some MacBooks famously also have a TouchBar that makes emoji easy to type. I can't remember the last time I had issues rendering emoji, and I have no idea why they'd be difficult to search for or how they would pose any accessibility issues.
I had no idea it was usable from the keyboard until I read this comment. There's a search box but it's invisible and hidden until you type blindly at a window that doesn't look like it accepts keys.
Terminal mostly supports emoji, but has many bugs. Some emoji, after being typed and deleted, don't properly restore the cursor to its original position.
ASCII may be ugly but works 100% of the time for me. I tried using emoji on macOS 10.14.5 Terminal just now and ran into every issue you said you don't encounter.
Re: Gitmoji – Yay or Nay?
#106Earlier quoted context omitted.
Doesn't 'fix' already mean there was a bug, that was 'fix'-ed?
> Doesn't 'fix' already mean there was a bug, that was 'fix'-ed? Read this: https://stackoverflow.com/questions/3580013/should-i-use-pas... TLDR from the Git repo: Describe your changes in imperative mood, e.g. "make xyzzy do frotz" instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behavior. People have different opinions on wh…
Re: Gitmoji – Yay or Nay?
#107Why do people feel the need to standardize these things? Emoji used occasionally are fun and refreshing and can draw attention to important commits. Emoji used by default become line noise. To paraphrase Goodhart’s Law, when a joke becomes a standard it ceases to be fun. I also object to the details of the categorization. Some tags split up tasks that really should be done together (eg fixing bugs and updating tests,…
Really? Because standardization leads to automation.
Re: Gitmoji – Yay or Nay?
#108> With gitmoji others or your future self can simply look at the associated emoji and straightaway catch the intention. Just like a word does. > The [bug emoji] emoji is easily recognized as a bug by most people The word "bug" works for me. > but will [tulip emoji] immediately signalize that code is removed? Nope. Besides, we already have commonly used symbols for that, "+" for a line added and "-" for a line deleted…
A caterpillar is not a bug. It is not institutionally recognizable as "bug" to me. A bug is a beetle or cockroach. I strongly suspect it's related to my first language being German, which maps "bug" and "beetle" to the same word "Käfer".
Though, I'll always think of this classic: https://jr.co.il/humor/humor007.jpg
Re: Gitmoji – Yay or Nay?
#109Earlier quoted context omitted.
> Emoji are hard to type on non-mobile platforms On Windows they are easy: + . Finding the right emoji is easier than on my Android phone as Windows lets me type the emoji name. Why emoji search is missing on Android... who knows.
That still seems much harder to me. Instead of just adding "PERF" to my commit messages, and later grepping for "PERF", I have to pull up a separate window each time, and remember that performance changes are indicated by a lightning bolt.
Tbh that's a very weak consideration, as it's ingrained through standardization throughout the codebase. And if this is for codebases you're not familiar with, then PERF is hardly gauranteed to.produce useful results (it certainly isn't standard in my own codebases).
Much more dangerous is people expanding on emoji-tagging with things like COLOR and similar VARIANTS, or an explosion of tags like being suggested in this article, making it even harder to use/memorize the system
But worst of all is that emoji are ugly and ruin the aesthetic of anything they come in contact with