Oh hey I just noticed this company has produced all of the recent "christmas" posts and sites on HN. Thanks for that!
Gitmoji – Yay or Nay?
141–150 of 224 posts
Re: Gitmoji – Yay or Nay?
#142Earlier quoted context omitted.
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
You've quoted me out of context. I was referring to handwriting. Besides, I would bet dropping the accent is more common than including it.
Re: Gitmoji – Yay or Nay?
#143Earlier quoted context omitted.
A decent chunk of programmers use GNU/Linux distros. Support is very lacking there.
"Programmers don't like this because Linux is shit" isn't a great argument against anything, really.
Git is for programmers. What other demographic should we be caring about?
If I'm an Android dev, it might bother me that application suspend is deliberately mishandled on tons of lower-end devices to improve battery life. Should I just ignore those users? If I'm making an email client, it might bother me that Gmail's IMAP support is crap. Should I stop supporting Gmail in my client?
Tools make concessions for the platforms and environments that they'll run in. They always have, and they always will. You get to ignore platforms if you're comfortable saying, "my stuff isn't for the users of those platforms." But so many programmers are on Linux, it probably isn't feasible for most OS projects to ignore them.
None of that means that Linux shouldn't have better emoji support. It should. It's embarrassing that it doesn't. But, you have to deal with the world as it exists today.
Re: Gitmoji – Yay or Nay?
#144Earlier 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…
> Is that an inherent property of English, or because we haven't invested enough effort into making non-English keyboards better?
It is an inherent property of English, at least in some way. English doesn't use diacritics or letters like the German "ß". It is the least common denominator of western languages.
AFAIK, languages that don't have English letters use an entirely different script, and considering that most programming languages, command lines, etc... use English, you need to be able to write English in addition to your native language.
English also have the interesting property that it is really simple to render, which makes it ideal for embedded software, low resolution screens, etc... Chinese a much too complicated, and even Hindi requires you to combine things.
Re: Gitmoji – Yay or Nay?
#145Earlier quoted context omitted.
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.
When you think about it a bit, you realize there just cannot be "generations" in that sense. People are continuously being born in each and every year. In a family tree there are generations sure, based on the levels of the tree, but not in a population.
The exception is special baby boom periods and their echoes, which do create some more "lumping" or births.
The worst is when people try to apply American generational stereotypes to other countries. Like, no, Hungarian "boomers" didn't grow up in plenty. The 50s were a period of terror and deprivation, not the "good ole days" of prosperity.
Re: Gitmoji – Yay or Nay?
#146I'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…
> they don't degrade gracefully for blind users
why not? there is a canonical plain-text description for every unicode emoji. at least in theory, i see no reason why a screen reader shouldn't be able to handle emojis.
Re: Gitmoji – Yay or Nay?
#147Why 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,…
>Why do people feel the need to standardize these things? Really? Because standardization leads to automation.
I'm not against automation in principle, but in this case you don't actually need to standardize before you automate.
Observation: people are prefixing their commit messages with emoji!
Automation: let's group commit messages by emoji, with an "uncategorised" bucket for emoji-less commits. Job done, that's all you need.
The "standard" that defines which emoji to use and when can evolve completely separately. I'd argue that this standardization is actively bad, as it adds to the learning curve when contributing to a project, stifles creativity (you may only use these emoji in exactly these ways) and wastes time by encouraging bikeshedding (people adding new categories, or arguing over existing categories).
Re: Gitmoji – Yay or Nay?
#148"Yay or Nay"?
Hell nay.
Re: Gitmoji – Yay or Nay?
#149Earlier 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…
As a person from another country speaking not-english, I just switch all my devices to english nowadays.
And imagine how much programming and debugging effort could be saved worldwide if everyone did as you and I do.
Re: Gitmoji – Yay or Nay?
#150We're considering it for our design system right now, but we're not sure how well it'll work with conventional commits and commitizen.
Are you sure you're not bikeshedding?
It sounds like you have several people discussing a change that's going to have a limited impact on outcomes, if any at all. Another warning sign is if people are having more fun arguing over the change than they would do actually using the new system.