How is the author the problem? What is the problem, in your view?

Creator of Orgro here.

> they only support a tiny subset of the format

I think Orgro's parser[0] is pretty complete at this point. If you can find an Org syntax that Orgro doesn't support, please let me know.

However I should be very clear here:

> they can't support any of the features that require the rest of emacs to be present which is a lot of of the value

This is absolutely true and unlikely to change anytime soon. As I'm sure you know, parsing the syntax correctly is not at all the same as supporting all of the features built on top of the AST.

[0]: https://github.com/amake/org_parser

This is the modern-day equivalent of asking the genie from the magic lamp for something, and getting something else that meets the letter but not the spirit of the request.

The smart thing to do is realize you don't know what you're doing, and don't rely on the genie at all. Or hire someone who knows how to tame the genie. Or whatever; someone else put it better: you fucked around and you found out. lol

I publish an app to the App Store, Google Play, and F-Droid. For years, F-Droid took absolute ages to reflect a new release.

People used to criticize the walled gardens for having capricious reviewers and slow review times, but I found F-Droid much more frustrating to get approval from and much slower to get a release out.

So this development is much appreciated. In fact I had an inkling that build times had improved recently when an update made it out to F-Droid in only a day or two.

> day to day transactions

Where is this happening?

Between me and my drug dealer

Lots of the rarer CJK ideographs are outside the BMP.

This was actually the first issue for my kanji learning app

https://github.com/runarberg/shodoku/issues/1

A classic utf-16 bug, where I failed to grab the two remaining bytes of these ideographs.

> it doesn't work for transitive deps unless those are specified by SHA as well, which is out of your control

So in other words the strategy in the docs doesn't actually address the issue

There's a repository setting you can enable to prevent actions from running unless they have their version pinned to a SHA digest. This setting applies transitively, so while you can't force your dependencies to use SHA pinning for their dependencies, you can block any workflow from running if it doesn't.

A lockfile would address this issue, with the added benefit that it would work

> There's no Noto Serif for CJK characters

Yes there is: https://fonts.google.com/noto/specimen/Noto+Serif+JP

> blowing it up out of proportion is just as toxic

One person decided that something wasn't for them. How is that in the same league as someone in a leadership position being unprofessional?

I personally don't care too much for hierarchies, so I didn't factor this in. You can be toxic at any level.

> You can be toxic at any level

And yet the context is extremely important.

> I didn't factor this in

That's how you get to false equivalencies.

>That's how you get to false equivalencies.

No, you're just putting something into it which doesn't matter to me. Not a false equivalency.

You said:

> blowing it up out of proportion is just as toxic

Making a false equivalency of the supposed toxicity of the commenter's post and the toxicity displayed in the article.

You can just take the L; you don't have to be performatively obtuse about it.

Might as well get rid of laws against murder because sometimes people commit murder anyway?

Not the same thing at all. There's consequences for murder, absolutely none for not abiding by this CoC; as clearly seen by the fact the posted remains as is.

A better analogy would be getting rid of laws against murder if its unevenly applied so people from a particular group always got away with it.