Now Google has decided to make theirs even worse than Apple at least when it comes to publishing in the play store.
Now Google has decided to make theirs even worse than Apple at least when it comes to publishing in the play store.
Every boxed Mac OS X came with a second disc containing the SDK (Xcode has always been an unstable cow, tho). They used to publish tech notes that explained how the OS works, rather than WWDC videos with high-level overviews that feel more like advertisements.
Back then they've at least made attempts to use some open standards, and allowed 3rd parties to fill gaps in the OS, instead of acting like a Smaug of APIs.
My graduation thesis was porting a visualisation framework from NeXTSTEP into Windows, Objective-C => C++, because my supervisor saw no future on keeping the NeXT hardware in our campus, if he only knew what would happen a few years later.
Microsoft is leaps and bounds more open than Google and Apple when it comes to development tooling.
It doesn’t excuse Apple’s behavior, but imo they still have a long way to go to challenge the track record of MS and Intel.
I even advocated for a previous company to try and find someone from the .NET project to help lead a similar but smaller tech transition.
This is better than the story from Apple and Google, who are just terrible consistently, but there is room for improvement.
I've had to make a couple of side projects for my company and I've tried WPF, Blazor, MAUI, and Winforms.
Blazor is the best out of all of these but even it has tedious boilerplate and unintuitive state handling.
MVVM makes WPF and Winforms a hassle, and customizing the looks of components is a nightmare, where some seemingly universal attributes will either get misapplied or outright ignored.
MAUI is a nightmare to work with. Cross compilation is both slow and opaque which makes it impossible to debug and since you are interfacing with the xcode compiler as well you are forced to debug using divine inspiration and hoping it works. We tried to make an RTC AR POC app a while back and it took me 2 weeks of trying different ways to make iirc arkit or webrtc to compile with dotnet and the result was us giving up and just making the iOS version in swift/using xcode instead. I think this is why I still have fond memories of xcode because despite all of its flaws it was noticeably better than trying to cross compile an iOS app from dotnet