Live data from Hacker News

Gitmoji – Yay or Nay?

opensource.christmas

131–140 of 224 posts

Re: Gitmoji – Yay or Nay?

#131

Earlier quoted context omitted.

How do I write a letter to my fiancé? What do I do when I want to take a break and go to a café? How can I write about that cornerstone of English myth and legend, Bēowulf?

Perhaps ſubſtitute a different letter.

Why, when we can use a proper encoding that actually contains the letters you want to use?

Re: Gitmoji – Yay or Nay?

#132
post #113

Earlier quoted context omitted.

You most certainly can. a-z A-Z 0-9 and , . ? ! ; : - ' " ( ) should suffice in nearly all cases apart from anything hyper specialized. You could probably write the majority of all English literature with only those characters, and there's more characters I left off. What other characters are "widely used" in English texts that are missing from ASCII

Accents and diacriticals are far from "hyper specialised", they are how many people are taught to write, and want to write. And - is not a dash, it is a minus. It does not suffice as a replacement for a real en or em dash in a properly typeset text. This is also not "specialised", it is how English is correctly typeset.

Source for claim many people are taught to use accents and diacriticals? Many people seem to have the opposite experience of being taught there are 26 unadorned letters in English.

Re: Gitmoji – Yay or Nay?

#134

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…

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.

Except, that's not really "easy". I prefer typing with buttons, not having to pull up a picker and search for each character. As others have mentioned, I don't want to pull up some window to grep through a commit log; I work very quickly in the terminal, and this would be an awful interruption to my flow.

Re: Gitmoji – Yay or Nay?

#135

Earlier quoted context omitted.

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 o…

Not to mention that transliterations aren't standardised (or rather, there are competing standards, and casually/colloquially people don't use any of them).

Even popular films released with Latin-alphabet names don't use the International Alphabet of Sanskrit Transliteration (IAST) for example.

It makes it hard as someone learning Hindi, because I might read or someone tells it's spelt 'k, u, l', but actually it's 'ka, la', i.e. kal or कल (yesterday/tomorrow) for example.

(And that's a common example, becauss IAST uses 'a' for inherent vowel, but many people write 'u', which is arguably often closer to the right sound if read as English, but that's probably not a high priority goal of IAST.)

Re: Gitmoji – Yay or Nay?

#136
post #69

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

> [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).

Set everything on fire.

Re: Gitmoji – Yay or Nay?

#137
I've gotten into arguments over whether or not emoji belong in the unicode standard at all, and I'm not going to rehash them here.

What I am going to say is that regardless of whether or not emoji are a good fit for unicode, they don't degrade gracefully for blind users (or for sighted users on older hardware) and they're prone to rendering issues between different fonts that can mask intent.[0]

Everything bad about icon fonts also applies to emoji. All of the articles you've ever read about how svg icons are preferred[1] -- all of them apply to emoji as well.

So in general, I only use unicode emoji[2] if two things are true

A) I'm in a closed conversation that won't be copied and pasted around or shared publicly.

B) I know the exact platform that my reader will be using to view my text.

I don't think Git falls into either of those categories.[3]

[0]: https://blog.emojipedia.org/apple-and-the-gun-emoji/

[1]: https://cloudfour.com/thinks/seriously-dont-use-icon-fonts/

[2]: I do heavily use emoji shorthands (:bug: :cat_eating_avacodo:) but these don't suffer from most of the same problems as emoji. They work as progressive enhancements for the platforms that render them, and fall back to readable text on the platforms that don't.

[3]: It's true that unicode fonts in general have issues when you get into non-English languages, but I don't advise people to avoid, say, Chinese characters, because: A) language glyphs don't change often enough to frighten me on accessibility, B) people who need to see them are likely already using devices that support their own languages, and C) we don't have a good alternative we could use instead.

Re: Gitmoji – Yay or Nay?

#138
I'd rather not but not because of the emoji but because atm I don't like categorizing commits in the first place. I've just tried doing it on a project and it felt pretty weird. Instead of just grouping single atomic changes like I'd usually do, I suddenly also have to think about what category fits a commit best and what to do if a commit satisfies multiple categories.

Thinking about it, emoji could actually help with this since it's easier to assign multiple categories to a commit without wasting a lot of character space. Still, what I'd rather want to see become a convention is an annotation in the commit's body that simply marks whether it's a major/minor/patch bump (or none). Plus optionally a line for the changelog. (Optionally because it allows commits to stay small while also not cluttering the changelog.)

Any thoughts/feedback/etc on this?

Re: Gitmoji – Yay or Nay?

#139
post #125

Earlier quoted context omitted.

You write just like everyone normally writes, by dropping the accent. I only see such spellings when people are trying to convey some sort of sophistication, rather than in casual, day-to-day use.

Precisely. Even when writing by hand, where there are no character encoding limitations, I've never seen anyone add the accents to "fiance" or "cafe" or "resume" when writing in English.

> I've never seen anyone add the accents to "fiance" or "cafe" or "resume" when writing in English.

We have café all the way from McDonalds up to Buckingham Palace.

https://www.mcdonalds.com/gb/en-gb/menu/mccafe.html

https://www.rct.uk/visit/the-state-rooms-buckingham-palace

Post reply on HN