Live data from Hacker News

Bye Bye Emojis: Emacs Hates MacOS

lunaryorn.com

81–90 of 181 posts

Re: Bye Bye Emojis: Emacs Hates MacOS

#81
1) It's perfectly okay (and good) that GNU maintainers do not want to have features that are needlessly exclusive to a given platform.

2) It's perfectly okay (and good) that they want their software to behave consistently across platforms, as otherwise those are not really cross-platform.

3) Coloured typeface are illogical, just use pictures, which is what emoji are. It's fairly easy to insert images into a buffer in Emacs.

Re: Bye Bye Emojis: Emacs Hates MacOS

#82
post #74

Earlier quoted context omitted.

Upstream GNU Emacs can no more be called "crippled" on macOS than it can be called "crippled" on linux, because on neither does it support multi-color emoticons. Maybe it seems "unfair" because macOS users could easily have the feature advantage over a free/libre OS user, but upstream GNU Emacs denies macOS the advantage. It is kind of funny. But also funny because GNU's adherence to their licensing philosophy means…

From the original article, Emacs had this feature, and then they removed it. That's crippling it. Deciding not to implement the feature in the first place, well, that's a reasonable decision given their desire for functionality to be cross-platform. But accepting it, then turning around and removing it later even though it was already implemented, that's just spite.

Crippling sounds like the entire software is unusable. If they stopped MacOS users being able to type the letter 's' that would be crippling. This is just disabling one small feature.

If crippled is a broken spine, then this is preventing some people from wearing a funny badge until everyone can wear funny badges.

Re: Bye Bye Emojis: Emacs Hates MacOS

#83
post #56
post #25

This kind of thing is exactly why I will always support and use Mitsuharu Yamamoto's macOS Emacs port ( https://bitbucket.org/mituharu/emacs-mac ), which has been consistently rock solid and committed to implementing nice to haves on macOS that this sort of political bullshit holds back on official development. Homebrew tap here: https://github.com/railwaycat/homebrew-emacsmacport

he is the author of the commit http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=934461...

And the commit seems to be in emacs-mac too - https://bitbucket.org/mituharu/emacs-mac/commits/9344612d3cd... (Going by the author date, it was in emacs-mac first.)

Re: Bye Bye Emojis: Emacs Hates MacOS

#84

Earlier quoted context omitted.

Deliberately crippling your product on Apple platforms does not in any way "remind users that it is not in agreement with Apple's treatment of its users". In fact, it's fairly ironic that, in an attempt to protest someone else's treatment of users, Emacs has decided to treat its users badly. Deliberately crippling Emacs will not make Apple change, and will not get people to switch away from Apple platforms. But what…

is removing multicolor font support crippling emacs?

I'd say it's a feature, not a bug. There is no place for colorful smileys in my text files.

Re: Bye Bye Emojis: Emacs Hates MacOS

#85
post #58

Earlier quoted context omitted.

You should not identify yourself with Apple's operating system. If I want I will identify myself with whatever I decide to identify myself with; I don't really care about Apple, but now you've turned it into a matter of principle, moralizing what people shouldn't do. You should not identify yourself with GNU/Linux. How did you like that? How about identifying oneself with JustWorks(SM), vertical integration, and thin…

I've always identified with ProDOS.

I always preferred SOS. More sophisticated.

Re: Bye Bye Emojis: Emacs Hates MacOS

#87

20 years ago the FSF had some very forward-looking ideas. Now we have the ornery opinion of old men - it was good enough for us two decades ago, it's good enough for you now. The point of free as in speech and not free as in beer is that the choice you make does not need to be right or wrong by the standards of other humans. Holding back technology because it's not available on "your" platform is just as monopolistic…

The point of free as in speech and not free as in beer is that the choice you make does not need to be right or wrong by the standards of other humans. No, it may be yours, but I'm pretty sure that was never the FSF's point. Not now, and not 20 years ago. Holding back technology because it's not available on "your" platform is just as monopolistic as any corporate entity they have butted heads with. - It's not "their…

It's not the FSF's point to have freedom of ideas? Then please explain what it's point is. You disagreed but haven't explained why.

If it's not "their" platform then how is it available elsewhere? If other distributors have access and can make it available then it is very much a GNU political standard and not a side effect the technology.

How are those platforms free if existing features have been removed due to politics? I stand by my point, 20 years ago the FSF was a foundation that wanted to make technology available to all - without having to worry about IP ownership. They have removed a feature that was technically sound due to it's status as a commercial work. How am I free to use this if I can only do so in designated zones?

Re: Bye Bye Emojis: Emacs Hates MacOS

#88
Feature parity across platforms makes it easier to develop and debug by removing platform-specific corner cases (of which there are already quite enough in Emacs). My init.el makes decisions based on which windowing system (if any) it's running on because some features work and some don't depending on the machine I'm on. I wish it didn't have to.

Re: Bye Bye Emojis: Emacs Hates MacOS

#89

As a product developer, maintaining a consistent feature set across OSes makes perfect sense to me. It is a struggle to get consistent behavior across different versions of Windows, let alone entirely different OS types.

On a technical level I totally agree, supporting tweaks and quirks in a codebase is a massive pain in the ass.

That's not the reason that has been given here - there was no claim that the technology was difficult to bring up to current spec. The reason was that non-GNU platforms had better font handling and now that's not allowed for a GNU project.

Post reply on HN