@argv_minus_one
> macOS scanning happens on an Apple server. App publishers must submit their apps to that server for scanning.

Oh, so I was closer than I thought: Apple hates #FreeSoftware so much that they won't acknowledge they *already have* everything they need to scan #Emacs for anything they want

and they petulantly refuse to do it unless the developer kisses the ring and submits to non-free conditions. And then complains *to the end user* that Apple failed.

@rossquantum

I'd phrase that as “Apple could not comprehend #FreeSoftware enough to use Freedom 1”.

Everything about #Emacs, *and this must include the build system*, is open for examination. Guaranteed by the license.

If Apple can't determine whether it's malware, and they pop up a big announcement of that? They announce their incompetence.

@rossquantum

@oantolin Emacs predates Lisp Machines. Emacs is an editor, nothing more or less. It is not a Lisp environment, or a Lisp implementation.

And yes, it is about Lisp, an extensible language. Emacs is special, but it is for other reasons.

#GNU #Emacs is a far shot from #LispM #LispMachine, and ZWEI is a far shot from #GNU #Emacs.

@oantolin There's tools and then there's tools. Before I got confident in #Emacs #Lisp I used to use (may god forgive me) Excel to do stuff like this.

Which was, I hope we can agree, unambiguously better than not being able to automate those processes. But not ideal.

We have lost so much in thirty or forty years, worst of all the autonomy to automate.

"But it feels like something from the seventies!" Yes, correct, that is exactly how it feels. Like something I can understand, control, and USE

@Zenie @lascapi @alternativeto In general: #Emacs is an island.

No groupware functionality, no shared/synchronized real-time editing, ...

Whenever you're on your own, #Emacs is a great choice (if not the best). Whenever you're working with other humans, Emacs is almost a complete fail at the moment from my perspective.

@publicvoit @lascapi @alternativeto

For me, nothing allows me to process email better than #emacs. #mutt came close. The primary function of email is writing and editing, nothing does that better than my editor.

Including, documenting and opening those emails is as easy as it gets.

I don't need to open some cumbersome GUI app that will make me use my mouse, just to read an email.

@lascapi @alternativeto IMO it's not important that you've got one tool that combines everything.

More important it that it is that flexible so that you can include/access/combine data and other tools as well.

Yes, #Emacs is probably *the* most versatile piece of software there is (and I'm using it since decades).

However, I don't use any of its built-in #email solutions (for reasons) but rather embed emails from my mail client (Evolution) so that I can link mails and open them very easily. That's the true power of advanced tooling, not the "one tool that does all of that".

And I'm aware of the irony of that message, considering the fact that Emacs has the power of including really anything(!) within its borders.

And of course: it's always better when it's FOSS and not closed source in order to minimize #lockin effects (besides proper standardized, open storage formats).

@alternativeto I miss something like that but for every #email account, based on #standards and #opensource !! 

I know that #emacs can do it, but it's too much for me!!!