Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gitmoji – Yay or Nay?

opensource.christmas

Post reply on HN
Print view View original

91–100 of 224 posts

Re: Gitmoji – Yay or Nay?

#91

Post by josteink »

FroshKiller wrote: post #80
josteink wrote: post #51

Nay. I'm clearly against this, and I don't find this kind of addition to the git ecosystem productive. And hopefully that won't translate into me being "hostile" towards women in tech, just because this was proposed by a woman.

It wouldn't have even occurred to me if you hadn't specifically mentioned it, which now makes me suspect it does have something to do with the fact a woman proposed it.

We have enough example of internet-outrage caused by tech-guys treating tech-women as peers.

That is outrage over "hostility towards tech-women" when what is actually happened was that guys criticized women equally as they would have criticized men. Even seemingly respectable organizations like the Linux Foundations have fallen prey to such nonsense fronted by (racist!) twitter lynch-mobs[1].

You'd think this be a pretty clear-cut case when considered objectively, but it has proven controversial, even here on HN.

In such a climate, it is only reasonable to pro-actively guard against such accusations. The troublesome part is that it's seemingly needed.

[1] https://twitter.com/hashtag/LinuxFoundationKangarooCourt

Re: Gitmoji – Yay or Nay?

#93

Post by zyx321 »

WalterBright wrote: post #71
Aeolun wrote: post #69

Earlier quoted context omitted.

> [tulip emoji] Is that what it looks like for you? For me it’s a flame (which seems to make more sense for removing code).

Yeah, it looks like a black tulip. As for a flame, I don't associate fire with removing things. Frankly, emoji and icons may work for things but they don't and never have worked for actions . Apple, for example, never did come up with an icon for "print" that people didn't have to be told what it meant. Apple could have saved a lot of grief by using "print" instead of the icon. (The same for "delete".) Back in my day…

I've seen websites using the fire emoji as part of their UI language to mean "hot (≙popular)"

But of course it's all too ambiguous to be useful. A "cash REGISTER" might just as easily be a "CHECKOUT counter" or more likely a "point of SALE".

Re: Gitmoji – Yay or Nay?

#94

Post by chrisseaton »

rahuldottech wrote: post #3

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

They are plaintext. They’re Unicode characters just like abc. There’s nothing special about them!

Re: Gitmoji – Yay or Nay?

#95

Post by sakisv »

As long as there is a non-emoji description of what is happening in your commit, use whatever you want. It's not something that I would ever use on anything semi-serious but I'm not going to forbid people who want to express themselves that way.

The one thing that I will forbid them to do though is use it in branch names - and especially in the beginning of the branch (if it's in the middle you can use tab completion). Your commit is something that I can read or I can use its hash, but branch names are something that I have to interact with directly and I don't want to have to copy/paste the name from github or trying to figure out how to type this emoji.

Re: Gitmoji – Yay or Nay?

#96

Post by GeneralMaximus »

AstralStorm wrote: post #47
GeneralMaximus wrote: post #45

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…

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, Hebre…

> The one thing English has going for it is the ease of typing it on any keyboard everywhere.

Is that an inherent property of English, or because we haven't invested enough effort into making non-English keyboards better?

Here's an interesting bit of data: ever since Google added support for Hindi in Google Assistant, it has become the second most used language used for voice search globally [1]. I don't know about other countries, but there's definitely a demand for non-English languages on computers in India.

> Romanizations are fine too.

No they're not. It implies you have knowledge of two separate languages, two separate writing systems, and the ability to convert between them. This is not always the case. People do write Romanized Hindi (and Tamil, Kannada, etc) in India, but that has more to do with the lack of native keyboards than anything else. With the rise of mobile devices, more people are writing Indian languages in their native scripts, thanks of the excellent work Google and Apple have done with their keyboards.

I'm as much a native English speaker as I am a Hindi speaker, and I'm entirely unwilling to accept a worse experience for either of these languages on my devices. Language is part of people's identities, and you can't really divorce language from script without losing something of its character in the process. People across the world have protested and rioted for their right to use their own languages. Governments are elected based on language issues. Supporting your target audience's primary language is part of your job as a good engineer, whether your target audience is non-tech people or other developers.

Where is this unwillingness to support multiple languages in software coming from, anyway?

[1] https://economictimes.indiatimes.com/tech/internet/hindi-sec...

Re: Gitmoji – Yay or Nay?

#97

Post by kalleboo »

mondaygreens wrote: post #31

Nay! Emoji is slang that excludes a huge number of people, not just due to preference but also because the meaning keeps changing and can be confusing if not exhausting to keep up with. It skews young and/or Western and there's far more kinds of programmers than that.

> It skews young and/or Western

How does it skew Western when they were literally invented in Japan?

Re: Gitmoji – Yay or Nay?

#99

Post by chrisseaton »

tadzik_ wrote: post #25

Nay, nay, nay. I don't like text that looks differently for everyone depending on the platform they're on. Emojis have shown us already that vendors are willing to change their appearance depending on current trends or political climate. Gun becomes water gun, salad becomes vegan salad. One day, if caterpillar becomes a butterfly because of some mundane idea, is it still going to be instantly recognizable as a bug? W…

> I don't like text that looks differently for everyone depending on the platform they're on.

But we already have fonts that make the Latin alphabet look different on different platforms.

> if caterpillar becomes a butterfly because of some mundane idea, is it still going to be instantly recognizable as a bug?

Yes? Didn’t Hopper tape a moth ‘bug’ into her notebook?

Re: Gitmoji – Yay or Nay?

#100

Post by oselhn »

rahuldottech wrote: post #3

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…

Exactly. Also I am pretty sure that every few months will someone find more appropriate symbol for each tag.
Post reply on HN