Development has dropped off a cliff over the last couple of months. The release cycle has moved from quarterly to yearly. He's basically taking his ball and going home. My guess is we'll see more internal initiatives like this AI builder instead of focusing on the core product.
This would be an okay strategy if his core product wasn't in such a state of disrepair. I've seen multiple issues on Github projects from Automattic developers saying "this would be easy to fix upstream but we're not allow to fix anything in WordPress right now." It's pathetic and actively harming his own business.
Also, good luck sending in a PR and getting it merged. Unless you are part of Matt’s inner circle, it isn’t happening. Even the most basic bug fix PRs are routinely ignored.
Indeed, you should probably just use "<details>" and "<summary>" for drop downs today (works perfectly without any javascript and have accessibility built in). CSS only dropdowns were a hack for an era before these elements were widely supported.
Someone has been running a massive fake DMCA notice bot targeting website contact forms with links to Google Cloud Storage files for the last year. I wonder if this is in response to this ongoing campaign?
I have a theory that they’re not actually intending to make it more touch friendly but rather they are trying to unify the interfaces between MacOS and iPadOS for when iPadOS supersedes MacOS. Slowly boiling the frog, so you don’t notice when they move iPadOS to the desktop.
It’s almost this but less extreme. They’re trying to unify the interfaces because they want to return to offering one app platform that isn’t sharply split.
iOS started as an OS X variant with special consideration for touch, but forked Cocoa. The unification that’s happening now isn’t about bringing iOS to Macs, it’s about merging Cocoa-next back into upstream.
I could see that. The reason I think it could be more extreme is the AppStore. I don’t have stats to back this up, but I would assume they make far more money from the iOS/iPadOs AppStore than Mac AppStore. It never truly caught on with the Mac, likely due to the long history of loading your own apps. Apple would love nothing more than to break this cycle.
Agreed. I think the long term strategy is to continue to iterate on iPadOS until it's close to feature parity with macOS and then drop macOS. It may take a decade or longer. Instead of rethinking the desktop UI to fit touch interactions, they're rethinking the touch UI to fit pointer interactions. The last major hurdle to clear is windowing, which you can see small steps towards in iPadOS 15.
I don't think people give enough credit to iPadOS's adaptive pointer. It's a complete rethinking of what a mouse should be in the context of current tech. It's a pointer that can adapt its resolution in different contexts. For UI's that do not need high resolution accuracy, it's much faster to target and click elements.
My instances have stayed up but I am having problems with API calls. If your instance is down, I wonder if it's isolated to CloudSQL Proxy connections. Seems like this could be an issue at the API level.
A few years back, I stumbled on the master transit plan for the Metro Detroit region prior to the freeway system being built. The original plan called for rail running in the median of the freeways, similar to how spots are in Chicago. The plan included artist concepts, layouts, etc. Not sure if its true or not, but I had read reports the auto industry fought the rail component of the project to its death.
It was a really fascinating document. It's somewhere on the internet; I wish I could find the link.
This would be an okay strategy if his core product wasn't in such a state of disrepair. I've seen multiple issues on Github projects from Automattic developers saying "this would be easy to fix upstream but we're not allow to fix anything in WordPress right now." It's pathetic and actively harming his own business.