[latexr]

> They're really not going to be able to dedicate resources to something as bijou as AppleScript.

They don’t need to do it themselves, they could just not stifle the efforts of third-parties who do want to and have worked on it. Multiple people started on it over the years and were simply ignored by the devs.

[array_key_first]

Probably because they don't want to take on that maintenance burden. Even just letting someone do that and merging it in is opening up a whooooole can of worms.

[latexr]

Then they should just say so and close the open issues, instead of letting them linger for literal decades and have people waste time on them then ignore them. That’s just bad stewardship.

Anyway, the reasons are irrelevant and I’m frankly tired of explaining this to Firefox defenders. Someone asked “what about Firefox are you missing” and I responded with what it’s missing for me. Plugging your ears and coming up with excuses doesn’t move the needle. Accept it or don’t, it makes no difference. In the meantime I’ll continue being honest with my users that I would like to support Firefox but I can’t, and many of them will keep switching browsers.

[array_key_first]

The features that firefox does not support are few and far between, and, IME, usually things you do not necessarily want supported.

As a user, I do not want nor need my browser to support AppleScript. AppleScript is something that should not exist. In somewhat typical apple fashion, it's some NIH platform-specific bullshit that nobody really cares about and is only half-assed supported even on it's native platform. The only way to deter Apple from creating these sisyphus-ian pieces of software is to just stop supporting them and force their hand to use something less bespoke. Although, Apple is not the only culprit of this - nor are they even the worst about it.

If I had my way, Mantle would not exist, iMessage would not exist, and some others. We would live in a perfect utopia and then we'd all hold hands and sing Kumbaya.

[latexr]

So first they didn’t do it because of the maintenance burden, and now it’s because the feature sucks and shouldn’t exist. If you’re going to keep ignoring my points and making up new things while moving the goalposts, I don’t see the point in having a discussion.

I’ll say it again:

> Plugging your ears and coming up with excuses doesn’t move the needle. Accept it or don’t, it makes no difference.

[array_key_first]

It's both, obviously. You asked for one reason, I gave it to you, you didn't like it, so I gave another reason. These are all speculative, of course, and just my opinion.

> If you’re going to keep ignoring my points and making up new things while moving the goalposts, I don’t see the point in having a discussion.

I'm not ignoring anything - it's called disagreeing with your points. Because I do disagree with them, to an extent.

I agree that Firefox is missing features. I DO NOT agree that this is generally, keyword generally, a bad thing.

Also, Firefox is not even the most behind browser. Uh, that would be Safari, and it's not even close.

If you don't support Firefox but you DO support Safari, then:

1. You must not give a flying fuck about web standards or features, as Safari is missing the most of both OR

2. You squarely target primarily Apple users so you have no choice but to put up with Apple's subpar software, i.e. you're Stockholm'd in

For option 2, the only way to stop that is to do what I said - stop playing Apple's games and don't target their bespoke barely-functional bullshit.

Also, let me just say: there is absolutely no shame in number 2. You have to make your money. Just a couple years ago, I was maintaining an application that still targeted IE 6. Yes, really. Sometimes you have to do what you have to do to reach the users where they are.

[latexr]

Everything about your answer is wrong and full of assumptions.

> You asked for one reason

No, I did not. I didn’t ask for any reason. I don’t need one, the result is the same.

> I gave it to you

No, you did not, you gave speculation. Which changes nothing.

> you didn't like it

I couldn’t care less about your speculation. I specifically said I don’t care. The only thing I don’t like is how you’re just making up reasons based on what you want and like, as if your tastes and needs are all that matters, instead of what’s the truth for Firefox development.

> I'm not ignoring anything

You moved the goal post without addressing my initial reply to your response, which poked a direct hole in your speculation:

> Then they should just say so and close the open issues, instead of letting them linger for literal decades and have people waste time on them then ignore them. That’s just bad stewardship.

You continue:

> it's called disagreeing with your points.

It makes no sense to disagree with a personal opinion! My reasons are my own. It’s like if you said you disagreed with me for saying I don’t like chocolate. Your opinion is irrelevant to someone else’s taste or needs.

And then the rest is just more speculation. Again, Firefox is the only major browser not supporting AppleScript. And just so you know, Chromium browsers typically support it better than Safari.