simonleeb

I agree that is a real risk, but imho past behavior suggests that "Apple" Apple and open-source Apple both can exist and it's likely going to be just fine.

On the plus side: Apple is paying many many real people to progress the language and tooling mostly in the open with solid community work.

Just as an example: JSON data - Including a Swift serializer adds code size, but bridging to JS is a bit less comfortable. And for each similar feature we will need to find a good compromise. We need to be careful not to create a "parallel universe" of Swift, where everything works completely differently from "normal Swift" - but at the same time things like 'import Foundation' won't fly on the web.

And, of course, things like HMR or "module splitting" and other more dynamic features are much, much tougher to do with a compiled language and Wasm. So, trying to reach "DX-parity" with JS frameworks can be a very pricy endeavor.

I think Swift adoption in general is also a ... factor. I personally think it is way more ergonomic to write than most languages, especially for UI and app-level stuff, while bringing a lot to the table. But as - we all know - it is still hasn't grown to its potential outside of Apple-land.

Embedded Swift is a moving target, but I am confident it delivers (it's evolving rapidly). Also, Wasm is a moving target to a degree.

And then there is just a ton to do, none of which a "great challenge", but just the grind of moving towards a "fully-featured UI framework"...

for years now I have been playing around with automation and DIY smart home technology, sliding deeper and deeper into this amazing world of fun projects and possibilities.

I found that one piece was missing: "semi-automation"

For certain things, fully automatic was not a good option for me (like turning off lights at night, or opening doors, etc.) - any automatic rule you would write would be very complicated and possibly still work against you sometimes.

What was/is really big of course is voice controlled stuff - and while it works ok most of the time, I just never got all to comfortable negotiating with these "smart" assistances.

I wanted quick, silent access to automation actions when they are relevant. Combining webhooks with iOS shortcuts was the best solution for me: Smart notifications to give me the right options at the right time.

With added location/time-based triggers and integrations for services like Zapier and Integromat, Pushcut is a great puzzle-piece for any automation project you want to have a say in.

Let me know what you think, internet!