No matter the value for money or compatibility, I will never leave macOS for windows because of it. I bought a hugely powerful windows PC in 2018 and the audio performance is awful compared to a 2011 macbook and my 2019 macbook is on another level.
Windows lack of attention to audio drivers is frankly staggering. CoreAudio 'just works'.
Maybe pay better attention to the sound hardware next time?
Windows audio drivers are so poor that they’re bypassed completely and basically all major hardware producers offer either ASIO drivers on windows or native CoreAudio drivers.
Using the same high quality external sound card, I get better performance on macOS with latency and buffer than I do on a windows machine with significantly ‘better’ hardware.
I know full well sound hardware makes a difference, and macOS and CoreAudio interfaces with said hardware significantly better than windows. There’s a reason producers of pro audio interfaces write their drivers natively for macOS and use ASIO for windows.
I’m talking about pro audio production tools here, not playing a few mp3s.
There’s a reason external hardware drivers are native on macOS.
Give me a native project over Web stuff any day of the week and I up for grabs, yet I do Web related projects since 1999.
Objective-C and Cocoa is great compared with the chaos of npm, yeoman, babel, node, deno, coffeescript, Typescript, bucklescript, angular, react, ember, dojo, prototype.js, jQuery, Vue, svelte, scss, and whatever someone comes up next month to improve their CV.
I am so happy that thanks to WebAssembly I am getting Flash back.
TBH Obj-C once you looked past it's ugly syntax is a better developer experience than swift today if your making large-ish apps. Today the debugger is still buggy, build times are still way slower and swift code bases create stutters in unresponsiveness inside Xcode to this day. And it was way worse back in the swift v1-3 days.
TBH I think swift could solve a lot of their build speed issues if they removed type inference beyond a very basic set and brought back fine file grained importing like you have with C and Java. You still get %95 the benefits with a couple of features that most IDEs like IntelliJ with java are shown to be NBD.
Stuff like Flutter & Kotlin Multiplatform might make a lot of this stuff moot although, and swift will be regulated as an iOS compatibility layer and a nicer looking C++
I think you meant Cassowary instead of Haversine: https://en.wikipedia.org/wiki/Cassowary_(software)
i have some feelings myself, but they are badly formulated so i wont say them here...
but im curious, specificaly why do you feel this way?
It’s basically the usual story with post-Jobs Apple: catering for the masses while neglecting the pros - but this time it’s about developers instead of consumers.
We have a finite cleverness budget; if you spend it on your code, then your product will suffer. If you build cleverness into the platform SDKs (hello SwiftUI! hello J2EE design pattern hell!), then every product on your platform will suffer.
Conal Elliott's work, while super interesting, does not cover the entirety of reactive programming. I found this[1] write-up to be helpful in defining what reactive programming is and it's value. The author is a member of the team working on Swift Concurrency.
And SwiftUI is compatible with anything from UIKit, so it actually doesn't hold anyone back who wants to try to do something non-trivial. If you watch the demos, particularly from the most recent WWDC, you'll see it actually makes quite complex behavior much more doable. Does that reduce the value of esoteric framework knowledge? Perhaps it does, but that means engineers now have more time to spend on the product not less.
As for SwiftUI, I guess the only issue it the current state of its tooling, as I have heard it still is found lacking.
Yet if one listens to iOS podcasts everyone is raving about it.
> With Swift and SwiftUI we seem to be heading towards a different future, and I’m yet to be convinced that it’s the right one.
The more things change, the more they stay the same...
...in your opinion. In the opinions of people who manage IT for the vast, vast majority of businesses around the world, where most of the serious software users exist, that title belongs to Microsoft Windows.
Apple is so overtly anti-consumer that I just can’t take opinions like this seriously. And Swift is a trash language with a shitty developer experience just like Obj-c was before it. They couldn’t even get strings right. Nobody wants it outside of Apple’s little bubble.
I can't even say "best" experience let alone "by far".
Apple is notoriously anti consumer on everything from hardware to software.
I don't know what you are talking about. They had a fun signup screen when you first boot your iPhone. I have 0 ideas what you are talking about for macOS.
I think their primary reason for success was their advertising/marketing.
Yet millions of people continue to happily give them money without being forced to, unlike say Microsoft or Google that you just cannot avoid even if you don't own any of their products.
I was a Windows/PC user for most of my life before I switched to Macs and in my experience Apple has been consistently more consumer-friendly than Microsoft or Google.
In fact my first foray into the Apple ecosystem was an iPad that I bought as a gift for someone, and fell in love with it so much I wanted to develop for iOS and bought my very first Mac for that. So far nothing has made me consider switching to Microsoft or Google.
The only thing I hate about Apple is their poor documentation and lack of official support on their own forums.
As in, you can easily avoid Apple if you don't own any Apple hardware.
Not so easy with Google or Microsoft.
It's not like you could leave Apple, you are locked in.
It may be hard to put into words why you feel that way. (which is why your post never mentioned anything about quality)
As mentioned opening the iphone box and giving Apple my personal information felt fantastic. The actual performance and quality was extremely dissapointing.
One could say the same for you, but that won't get us anywhere.
> It's not like you could leave Apple, you are locked in.
I have lived most of my life without Apple and I know how to do it again.
Tell me, how do you avoid Google or Microsoft?
I was happily using GitHub before Microsoft bought it.
I was happily using YouTube before Google bought it and made it worse.
I can't avoid feeding my data to Google even if I don't use any of their services, through their Ads, Analytics etc. and who knows what kind of shadow profiles they build from just my proximity to their other users.
Now, every time I sign into YouTube I have to delete all Google cookies to avoid being automatically signed into Search.
> As mentioned opening the iphone box and giving Apple my personal information felt fantastic. The actual performance and quality was extremely dissapointing.
I've been using the iPhone since the 5S and honestly, every time I have to handle someone's Android (e.g. to show them how to do something quicker than telling them), I want to hand it back as soon as possible.
If you haven't taken a marketing class, I highly recommend it.
Let me ramble a bit here.
Apple’s platforms had always put users before developers, that’s why they were so successful. They’ve built the best user experience by far using nothing but a simple Smalltalk-esque language from the 80s. Look at their frameworks: CoreAudio, CoreAnimation, UIKit... Tremendously powerful, and the best in their league - in terms of possibilities, not necessarily developer experience! Others were shoving garbage-collected virtual machines in their devices, piling abstraction over abstraction, “fluent APIs” (remember those?); meanwhile Apple built an empire with this quirky dynamic language (plus some C++ under the hood), where you had to do manual reference counting as late as 2012! Developers were livid. “How am I supposed to program in this weird language?” “AutoLayout? Why can’t it be just like CSS or something??” But Apple didn’t give a shit, they knew their platform, their frameworks were the best, period. And whiny devs had to adapt to gain access to the richest cohort of users in the computing landscape.
With Swift and SwiftUI we seem to be heading towards a different future, and I’m yet to be convinced that it’s the right one.