@fastfinge Hmm, I daily drive remote and don't mind whether it's core or addon, but that feature alone is invaluable. Did it need to be core? Probably not. Is it better for it in my personal view? Possibly. Did the 2026.1 issue where, if your network wasn't ready in-time, you jus wouldn't fail to connect to a server cause me some problems? Yes. Could it have been solved if it was still an addon? Yes, with 3 minutes with Codex/<insert LLM here or programming knowledge if you're cooler than me> Core, I just didn't touch it. I waited and hoped it would get solved and 2026.1.1 might have solved it. I haven't rebooted recently to find out. Remote on the whole though, absolutely necessary. The rest of the article, no real comment. Haven't been adversely affected.
@FreakyFwoof I completely agree that it's required. But does that mean it should be in core? I dunno. Like I say, reasonable people can disagree. But I notice that Apple has started moving apps (apple sports, apple invites, etc) out of the main OS so they can maintain and update them seperatly.
@fastfinge@FreakyFwoof Right, but it's Apple and we know that they will take care of those apps in due time. With the Remote add-on in particular, I mean the original Remote, it was oftentimes updated terribly late as if it had been ditched by its own devs altogether.
@amir@FreakyFwoof Could NVDA have taken over maintaining the addon, but not have made it part of core? That way, it could be updated separately from NVDA. Maybe that would have made maintaining it harder somehow? I don't know. To repeat myself again: "I'm probably missing context, so I'll just have to trust that NVAccess knows things I don't." That phrase is doing far too much work, I think.
@amir@FreakyFwoof And the idea that "We've never done it that way, because we don't do that, so it can't be done." is another alarming sign of shallow decision making. Also, NVDA has never moved an addon into core. So they're already doing things they've never done before.
