Retroactive VS WHATWG HTML Standard

No need to keep Mojave to run iTunes — iTunes can be run on newer macOS, by using Retroactive [1] to patch it.

Regarding running a newer macOS on older hardware, check out OCLP [1] — do make sure you make full backups and have a working recovery plan before trying anything with OCLP though. I know that might sound somewhat obvious to a lot of folk, but you'd be surprised at the amount of folk that jump in and try OCLP on their main system without any backup plan.

Note that are some gotchas re installing OCLP on some older h/w, and it will help to read up on possible issues before wading in. e.g. during installation it might be necessary to use a wired keyboard and mouse, via a USB hub, until the installation is done, you might also need a wired network connection during install, similarly. Depends on h/w (I've not patched MacBooks myself, yet). Once the patcher is done, these should not be needed anymore.

Official support for OCLP is only via Discord — but there is a very active unofficial peer/user support group on FB [3]

HTH!

[1] https://github.com/cormiertyshawn895/Retroactive

[2] https://dortania.github.io/OpenCore-Legacy-Patcher/

[3] https://www.facebook.com/groups/opencoreprojectlegacy

Or use Retroactive.

That said, my 2020 Mac Mini M1 also works great with the USB iPods - I used an app called Retroactive to get iTunes 11.4, which works fabulously to load my iPods. Can't say how well it works with the Firewire iPods, as I don't have all the requisite Thunderbolt adapters to make it work.

There's a project called Retroactive https://github.com/cormiertyshawn895/Retroactive/ that lets you install iTunes 10-12 on Catalina and newer OS. You could do that and still keep your playlists, etc.

you can run Aperture on newer Macs https://github.com/cormiertyshawn895/Retroactive/ just in case you want to check.

WHAT-WG HTML

There's a long-standing WHATWG feature request open for it here: https://github.com/whatwg/html/issues/2791

And several userland custom element implementation, like https://www.npmjs.com/package//html-include-element

One of the cool things that you can do with client-side includes and shadow DOM is render the included HTML into a shadow root that has s, so that the child content of the include element is slotted into a shell implemented by the included HTML.

This lets you do things like have the main page be the pre-page content and the included HTML be a heavily cached site-wide shell, and then another per-user include with personalized HTML - all cached appropriately.

The `allow` attribute on iframes is a relatively recent API addition from 2017

https://github.com/whatwg/html/pull/3287

I think there's a pretty strong argument at this point for this kind of replacing DOM with a response behavior being part of the platform.

I think the first step would be an element that lets you load external content into the page declaratively. There's a spec issue open for this: https://github.com/whatwg/html/issues/2791

And my custom element implementation of the idea: https://www.npmjs.com/package/html-include-element

Then HTML could support these elements being targets of links.

> Consider https://www.ietf.org/rfc/rfc1866.txt vs https://html.spec.whatwg.org/multipage/

I thought, oh, that's not so bad. Then I realized what I was looking at was a 10 page index.

I'd love to see something like HTMX get standardized, but I'm extremely pessimistic for HTMX's prospects for standardization in HTML.

In talking to a few standards folks about it, they've all said, "oh, yeah, you want declarative AJAX; people have tried and failed to get that standardized for years." Even just trying to get

to target a section of the page that isn't an has been argued about and hashed out for years.<p>Why is that? Well, for example, here's the form you have to fill out to start standardizing a front-end feature. <a href="https://github.com/whatwg/html/issues/new?assignees=&labels=addition%2Fproposal%2Cneeds+implementer+interest&projects=&template=1-new-feature.yml">https://github.com/whatwg/html/issues/new?assignees=&labels=...</a><p>It asks three main questions:<p>* What problem are you trying to solve?

The issue with a single global event handler is discussed here: https://github.com/WICG/close-watcher#a-single-event

If you use popover="", you get the kind of functionality you're discussing for free. For

, the discussion is in progress and reaching a conclusion: https://github.com/whatwg/html/issues/9373