Live data from Hacker News

Gitmoji – Yay or Nay?

opensource.christmas

41–50 of 224 posts

Re: Gitmoji – Yay or Nay?

#41

That'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…

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.

Re: Gitmoji – Yay or Nay?

#42
Nay.

> A picture says more than words

Because it relies on a lot of cultural background. Which in the world of emoji changes fast. This won't be welcoming of new users when they have to learn 10 or more symbols for whatever you're doing.

:lipstick: for UI changes? Why? :computer: or :smartphone: as those are the usual interface used or ️:wheelchair: because you care about something accessible would feel better.

Re: Gitmoji – Yay or Nay?

#43

Earlier quoted context omitted.

Sorry, zoomer? Not familiar with that term

It's a way of segregating people by age, then acting derisively about various groups in response to that. You identify bad character traits, call them out with the relevant "generation" phrase, and then sneakily imply that they have that character trait because they're within that age range (even when they're not).

The worst part of it is that this obsession with "generations" is almost exclusively tied to the US. In most countries, this concept is not part of the memescape at all, so it's even more confusing.

Re: Gitmoji – Yay or Nay?

#44

I like it! I agree with many of the objections in other comments, but used wisely emojis in commit messages can definitely add value. 1. They add easy noticeable visual cues that might otherwise require reading a full sentence (at that often will be omitted altogether). 2. It's fun and informal, something that's often lacking in dev teams.

It’s fun and informal until somebody tells you it’s mandatory.

Re: Gitmoji – Yay or Nay?

#45
post #36

That'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…

> Please use good ol' plaintext I want to emphasize on that. Why do programmers like plaintext, often to the point of wanting ASCII instead of unicode despite its international awesomeness? That's because we are called when things break down in the machinery. Monospace ASCII may look boring, but it has a precious characteristic: there is (almost) 1-to-1 mapping between the inner representation of a character and its…

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 speak while doing my job. Especially when I'm building products that eventually get translated into five or six different languages, all using different scripts.

This is one reason I prefer using GUI applications over CLI applications: Unicode support is terrible across terminals and CLI apps, while most of the commonly used GUI frameworks are okay.

If your app has no issues rendering हैकर न्यूज़ (Hacker News), then it should have no issues rendering Emoji. If your app cannot render that bit of Hindi text, then the problem is your app and not Unicode.

Re: Gitmoji – Yay or Nay?

#46
post #4

My main concern are blind people, I‘m not sure how well these emojis are accessible for them.

macOS VoiceOver reads one of the (but not necessarily the most useful in a given context) names of the emoji. For example, gets read as “caterpillar”. However, importantly: there’s no distinction that it’s an emoji when read. Caveats: I have no idea what JAWS does here. I’m not a visually impaired user, but have done a11y work in the past.

Too late to edit now, but just realized HN scrubbed the emoji. “…For example, gets read…”

Re: Gitmoji – Yay or Nay?

#47
post #36

Earlier quoted context omitted.

> Please use good ol' plaintext I want to emphasize on that. Why do programmers like plaintext, often to the point of wanting ASCII instead of unicode despite its international awesomeness? That's because we are called when things break down in the machinery. Monospace ASCII may look boring, but it has a precious characteristic: there is (almost) 1-to-1 mapping between the inner representation of a character and its…

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…

Yes, also my problem is not understanding every language in the world and how to use a Chinese keyboard to type this in. (Yes, I know this is not, I'm being facetious. OP probably cannot use it either. If not, substitute 3-bulsik Korean.)

The one thing English has going for it is the ease of typing it on any keyboard everywhere. Romanizations are fine too. Heck, even Russian is a bit problematic. Much more CJK, Hebrew, Arabic and Indian languages.

Emoji are easier to type in.

Re: Gitmoji – Yay or Nay?

#50

Earlier quoted context omitted.

macOS VoiceOver reads one of the (but not necessarily the most useful in a given context) names of the emoji. For example, gets read as “caterpillar”. However, importantly: there’s no distinction that it’s an emoji when read. Caveats: I have no idea what JAWS does here. I’m not a visually impaired user, but have done a11y work in the past.

Too late to edit now, but just realized HN scrubbed the emoji. “…For example, gets read…”

An object lesson in the problems of using emoji to actually convey meaning :)
Post reply on HN