Exactly my thoughts after reading the article. I am surprised that so few have pointed this out because it entirely invalidates the article’s conclusion for any serious usage. To stay at the USB-C example: it‘s like plugging in a Toaster into a monitor but the Toaster changes its communication protocol every time it gets reconnected.
Exactly my thoughts after reading the article. I am surprised that so few have pointed this out because it entirely invalidates the article’s conclusion for any serious usage. To stay at the USB-C example: it‘s like plugging in a Toaster into a monitor but the Toaster changes its communication protocol every time it gets reconnected.
I am very excited for this. One question I couldn’t find an answer for though is whether the hardware is open enough to be usable with other home automation systems. I am using OpenHAB and they too have an integrated voice assistant. I looked into migrating to HA a couple times but eventually gave up, primarily because it felt like such a waste of time to migrate a fully working environment with dozens of rules and scripts to yaml files.
It's all open and so should be able to work with OpenHAB as well but it would need somebody to either write a firmware that's compatibale with the OpenHAB endpoints or add ESPHome interegeation into OpenHAB. Somebody might have already done that for their voice stuff.
There is not much yaml in home assistant now unless you want it. I'd give it a go in a VM and see what it finds on your network :)
> Warning: there’s a bug right now that crashes the app in macOS 15.1. […] I’ve tested this with Xcode 16.0 beta 6 and Xcode 16.1 and they both act the same. But on a computer running macOS 15.0 beta 7 and Xcode 16.0 beta 6, it works perfectly. So this is a bug in macOS 15.1.
One of the reasons I've left development for the Apple ecosystem is that these things happen all the time. They are tedious to fix and often require reverse engineering their system.
There is also something to be said for being a developer in an ecosystem that is actively hostile towards you and your interests as a software developer.
It looks a lot like Stockholm syndrome from the outside at least.
But I genuinely don’t understand how or why anyone would pick up native iOS / MacOS development in 2024. It seems like an incredibly shit medium to long term bet.
My reason is that frameworks are generally more wide and deep than can be found elsewhere. It’s not difficult at all to build a polished app with nothing but Swift and AppKit/UIKit, with few or no third party libraries, which is increasingly rare in my experience (certainly not the case with WinUI or Android Framework). The next most comparable thing is Qt Widgets, but that’s for practical purposes restricted to either C++ or Python and is seemingly not receiving much attention any more than it’s been decided that the more “bring your own everything” style Qt Quick is the star of the Qt show.
AppKit/UIKit aren’t afraid to be opinionated either which is occasionally annoying but 90% of the time a good thing, because that makes for tested and supported happy paths that work well. Android Framework is the biggest contrast here, being littered with multiple half-baked ways to do everything, none of which Google has shown any particular preference toward until in just the past few years.
What would get me to move for my personal projects is something with that solidly “batteries included” aspect to it (there’s no excuse for needing to rope in a third party library to get something as mundane as a scrolling sortable table view with headers in a desktop UI framework, that’s like new cars coming without wheels) and similar opinionation, along with support for Swift or compiled Swift-like language.
I dunno about MacOS but iOS is a potential market of billions of users; for that kind of market people are willing to eat a lot of shit sandwiches. And there's plenty of markets where the development tools are much, much worse.
Until you're not allowed to anyone. You get the higher risk and higher reward with them and just have to hope they're not looking at your app specifically today.
