It's nice to see the improve focused on AI and recognition of their past missteps. So far out of all the announcements this past month, I think this will be the most significant. The increased emphasis with on device models is exactly the right move. I'm tired of sending data out of my computer when it isn't needed.
I think we are talking past each other because we are optimizing for different domains.
You seem to want the ergonomics of a structural type system like TypeScript where data shapes are fluid but explicitly unsound [1]. In that paradigm requiring a named Enum feels like clutter because it forces you to pause and define a relationship that you just want to infer.
But Swift is a nominal static language designed for long lived binary compiled applications [2]. In this context that clutter is actually architectural definition. The friction is a feature not a bug because it discourages passing around anonymous bags of data and forces you to model what that data represents.
Swift actually has plenty of sugar but it puts it in places that don't compromise static analysis. It is designed to be expressive without being loose.
Complaining that Swift doesn't handle anonymous unions as easily as TS is like complaining that a tank handles worse than an F1 car. It is true but the tank is built to survive a direct hit whereas the F1 car trades that safety for raw speed.
I think you’re conflating 'conciseness' with 'correctness.' The 'clutter' you're describing in Swift like, having to explicitly define an Enum instead of using a vertical bar |, is exactly what makes it more robust than TS for large-scale systems.
In TypeScript a union like string | number is structural and convenient, but it lacks semantic meaning. In Swift, by defining an Enum, you give those states a name and a purpose. This forces you to handle cases exhaustively and intentionally. When you're dealing with a massive codebase 'easy' type bridging is often how you end up back in 'id' or 'any' hell. Swift’s compiler yelling at you is usually it trying to tell you that your logic is too ambiguous to be safely compiled which, in a safety first language, is the compiler doing its job.
I know it might sound cliche but walking is an easy habit to start and keep up with. I tend to walk when I get stuck on a problem and try to distract my mind with something else. Usually this turns into my subconscious working through the problem until I get an idea to try out.
The health benefits are very nice too if you’re just starting out. There are diminishing returns as your body gets used to it.
15 minutes in the morning/afternoon is my usually habit while at work. But on particularly tough days or just ones with nice weather I’d go for much longer walks.
It’s nice to explore the spaces around you when on these walks. You’ll end up discovering more of your surroundings than you’d ever expect. One nice benefit I’ve found is that I can do a 35ish minute walk to the movie theater I’d normally drive to. Doing this lets me just go see a movie on a whim, eat at one of the many restaurants near it. Maybe get a little drunk and be able to walk off a meal/buzz on the way back. I’ve had many epiphanies in this state of mind. You’ll just be a more relaxed individual if you adopted this.
I think you might be mistaken on the height of the card, if you look at the ports they are mini-DP on a low profile bracket. The picture also states that it includes both types of brackets.