That’s really not a fair statement from him given:
1. Based on their github orgs, there is effectively no separation between wordpress.org and Automattic.
2. The core WP contributors trac has a long history of not really being welcome to new contributions. Outside of the design decisions coming from Automattic, third party contributions either die in multi-year deliberations or get directed to the plugin system.
3. The development culture around WP, which largely revolves around the plugin ecosystem - has always trended towards paid plugins over OSS software.
A hyper-fixation session feels closer to how people describe addiction than I’d like to admit.
When unmedicated, I can easily find myself diving down the rabbit hole for 12-14 hours straight, working on interesting but unimportant tasks.
You forget about any concept of time. You feel hunger but can’t pull yourself away to eat lunch or dinner. Daily goals are forgotten. You only stop when your body literally forces you.
Around 2009, I found a bottle of “grandma’s original molasses” from the mid-90s which the nutritional facts claiming had 30% DV of iron. I compared it against a new bottle at the time, which listed 10% DV.
The HATEOAS approach is viable for some applications but I wouldn't necessarily call it the future.
Using custom html attributes as the base for complex client-side interactions is arguably a step backwards when considering the story around maintenance.
Right now, if you are building a robust component library - it's much easier to maintain using a template language with strong Typescript / IDE support, like JSX or similar.
Instruct your Tailscale invitees to download the app and voila, simply toggle it on or off as needed.