They also say:

> Please note that Rosetta functionality for older, unmaintained gaming titles that rely on Intel-based frameworks will continue to be supported.

I interpret that to mean just enough of Rosetta and Intel frameworks will continue to be around, at least for macOS 28. Not specified which ones, or whether it stays any longer than that.

I’m pretty curious of what that will look like exactly, because there’s a fair amount of system frameworks/libraries needed to get to a bare minimum “hello world” AppKit app. Add on top any number of other frameworks that might be used by “older, unmaintained” games that Apple sees fit to keep supporting. Does this ensure OpenGL is kept on life support? Will they consider Wine important enough to support, perhaps even after they drop native Intel games?

I do consolidate most of the expenses with my other projects, and ads cover most of the costs, but we’re planning some future projects such as hosting of custom Windows updates (opt-in) that will get expensive. So this will matter a lot more soon enough.

1. Files come from Wayback Machine, which is trusted to serve legitimate snapshots

2. There is a sha1 and size listed for most files (though these come from Wayback)

3. Checking signature is easy enough from Explorer

Perhaps a page on “how to know this is legit” is a good idea to help educate about this. The goal of the project is to have legitimate downloads with good SEO, without having to cut through ads/spam/sketchy redirects (still has a few ads but intentionally non-obtrusive), so people aren’t blindly downloading from sketchy sites.

Web engines were honestly not great back then. WebKit was ok but JavaScriptCore was very slow, and of course that’s what iOS, Android, and BB10 were all running on that slow hardware. I have distinct (bad) memories that even “GPU-accelerated” CSS animations were barely 15fps, while native apps reliably got 60fps unless they really messed up. That’s on top of the infamous 300ms issue, where every tap took 300ms to fire off because it was waiting to see if you were trying to double-tap.

So I really think some of the blame is still shared with Apple, although it’s hard to say if that’s because of any malicious intent to prop up the App Store, or just because they were under pressure to build out the iOS platform that there wasn’t enough time to optimise. I suspect it was both.

Original: https://github.com/samhenrigold/LidAngleSensor

Demos (no farts, sorry): https://hachyderm.io/@samhenrigold/115159295473019599 https://hachyderm.io/@samhenrigold/115159854830332329

That said, every time I’ve tried it, it’s spent ages writing code that barely works, where it keeps writing over-engineered workarounds to obvious errors. Eventually, it gives up and decides broken is good enough, and returns to the prompt. So you still have a point…

> There's an NFS app for macOS called NFS Manager from Germany's Marcel Bresink.

> On pre-15.5 Macs, see the Terminal AFP command mount_afp by opening Terminal and typing:

> man mount_afp and pressing Return on your keyboard. To exit the man system, press Control-Z or the q key.

> Several third-party NAS vendors, such as Synology and others, include AFP support in their products, but that's likely to come to an end soon too.

(Not clear why it would be coming to an end if they’re based on Linux!)

The cached headline I saw on Mastodon also called it “depreciated”.

Losing AFP sucks, because macOS’s SMB support continues to be abysmally slow, and really needs Apple’s undocumented proprietary SMB extensions to work halfway decent. Lately I’ve been accessing my SMB shares (from both Samba and Windows 11) through Cyberduck, because Finder is just unbearably slow and gets tripped up on file permissions for no reason. Deprecated or not, Netatalk will be more important than ever if users need a protocol that just works.

And I’m sure Mozilla is furiously looking around for new funding sources right now, governments could be of interest, but I expect them to be very careful about letting money influence the product. They know their independence is a key feature, and Google has so far allowed them to remain independent aside from default search engine choice.

The ways they’ve acted a bit on the sketchy side are perfectly reasonable to call out, even if the writing here is a bit thin. Some are sloppy bugs that shouldn’t have been allowed to happen (.onion DNS leakage), but the rest were intentional decisions (replacing ads, soliciting donations in creators’ names, affiliate injection).

I feel it’s quite difficult to recommend anyone ever use a browser other than the main 4 (Firefox, Chrome, Edge, Safari), because of things like this. All of those have had between 16 and 30 years of experience poured into them, full-time engineers working deep in the JS/layout/etc engines, and they have a fat budget to keep it all going. Startups like Brave, Browser Company, etc. don’t quite have such resources, are very reliant on the benevolence of Google/Mozilla/Apple, and need to keep watching their back to make sure they’re still profitable. Completely FOSS community projects like Ungoogled Chromium, Librewolf, and Zen don’t tend to have any security experience on the team, or any auditing going on, nor the funding to hire for any of those skills. It doesn’t feel responsible to tell someone to download one of these browsers and then go and log into their email, bank, government accounts, etc. on it. As much as we want projects like this to succeed and beat the Google/Apple-centric monoculture we’re stuck with.

I think Mozilla’s past decade would have been very different if he were able to stay as CEO. He’s clearly managed Brave as a startup well enough that it’s still in operation - now imagine what he could have done with those Google billions. There wouldn’t be any need for BAT or new tab sponsored links or injection of affiliate links (this all may change soon of course). But in the current situation, there are some legitimate concerns with how Brave operates or did so in the past, which aren’t likely to be fixed because they require it to work this way to be profitable.

https://en.wikipedia.org/w/index.php?diff=1232511036&oldid=1... https://9to5mac.com/2015/03/14/apple-invent-usb-type-c/