3,602 karma · joined August 11, 2011
There are many long magazine articles discussing whether wokeness is a religion or cult. Either way, it has completely derailed all political discourse for the benefit of the most privileged (as defined by money).
And in the media world, it means that everything is now over-the-top preachy, and that scoring political points has become more important than making good art. Sucks, but at least there are plenty of classic movies to re-watch.
Plus first-party apps like Safari with its fluid trackpad gestures, Photos with its iCloud integration, and of course Xcode, because being able to build/debug things for macOS/iOS is a bonus feature I can offer as a developer.
The list is a lot shorter than 10 or 15 years ago. Most new apps that come out are Electron, but even then there's sometimes no Linux port (Trello, WhatsApp).
But if I go and buy a random Windows _laptop_ and try to slap Linux on it, I might have all sorts of issues with the trackpad, webcam, fingerprint sensors, never mind sleep/wake.
That's why Linux laptop vendors are a thing and deserve our praise (just like the companies you've mentioned)! All I'm saying is that Apple is hardly the only company left that doesn't actively support Linux.
When I was shopping around a few years ago, the fingerprint reader even on Dell's Linux-focused developer laptops was dead. I liked the Razer Blade, but many components didn't support Linux; looks like the trackpad on some models still doesn't work.
If "any vendor" actively supported Linux, we wouldn't need companies like Framework or system76 that pick compatible components. I'm not saying that Apple is particularly helpful, just that they're hardly alone in not caring about Linux.
Apple doesn't provide Linux drivers for their components, but neither does "anyone else", sadly.
But it means that Linux on M1 Macs might actually happen in the near future.
Edit: And Windows doesn't run natively/officially on M1 Macs because Microsoft has a stupid exclusivity deal: https://www.macrumors.com/2021/11/22/microsoft-qualcomm-arm-...
What annoys me is that AppCenter takes up so much space in their blog posts and sponsoring campaigns, because I feel it's the worst of their apps. The navigation model never made sense to me (why is search disabled when I'm on "Installed"?). It also doesn't look good, because there are way more tiny utility apps than there are good icon designers, and often the icons are just shown on a giant, colored rectangle because apps have no banner images.
I wish they'd do it more "magazine-like" as Apple does, just with more unsplash images instead of Apple's terrible Corporate Memphis illustrations.
In my experience, Apple doesn't even have to freeze anything because the iOS developer community (outside of Apple) is full of proud Early Adopters. Sometimes it feels like a race to use the latest tools on day one. I haven't seen anyone looking for ObjC developers from the day Swift was announced.
On the other hand, the Smalltalk model would not have worked for SwiftUI. It really feels like Apple has bet the farm on the next generation of libraries/frameworks.
It's extremely unhealthy for web standards that every deviation from Chrome's behavior is considered a nonsense bug now.
Just anecdata, but from walking through German trains, I disagree. I still see non-Retina MacBook Airs on some trays, for example, last sold in 2015.
Some Mac models are clearly more reliable and maintainable than others, see the butterfly keyboard fiasco. But I think companies should be judged by their better products, not the duds.
For example, the offshore Swift programmers I've encountered will add "?? 0", "?? []" etc. into expressions involving optionals until they compile. That doesn't mean that Swift's nullability is pointless, it's still a great tool for diligent programmers.
Just observe how much the iOS community talks about Swift patterns. Objective-C was more like Go, in that you accept your fate, keep things simple, and write some boilerplate code here and there. It seems to drive some people crazy, but it also avoids C++-style meta discussions about language features.
Whether this trade-off increases or decreases productivity depends on your team.
Except for a couple of malloc'd C arrays (as an optimization over using NSArray<NSValue>), most of it was for interop with C libraries, the same code where in Swift you'd have to use UnsafeMutablePointer.
Or they are working in a small and well-funded company that only employs ~10x engineers, and they have never met a (to them) 0.1x engineer.
I also wonder if parties like The Third Way or the far-left ones aren't partially ops to split the vote on the ends of the spectrum.
Not AfD by the way, but "Der Dritte Weg", a party that I learned about through the Wahl-O-Mat.
[1] https://www.welt.de/regionales/nrw/article163830133/Hier-koe... [2] https://www.br.de/nachrichten/bayern/landgericht-verbietet-e...
The mudkipz catchphrase was also very forced. Reminded me of the "hello fellow young people" meme. Of course, it might all be intentional.
As much as I love to hate Atlassian, I feel like complaining about Atlassian is like techies complaining about management in general. Every single anecdote is both terrible and true, but it's not quite as easy as it seems to do it better.
I think even that would be a good attack vector against Atlassian: For them, "integration" means adding links from one product to the other. If I were to pay for an integrated suite of tools, the least I would expect is that their bloody markup languages are consistent. But because Atlassian just buys random products and then doesn't seem to ever change a single thing about them, that's not going to happen.
To give some context, I remember reading an article about massive view controllers and one example was Firefox for iOS, so I've dug up a snapshot of its main view controller, which exhibits all the things people hate about Apple's MVC:
https://github.com/mozilla-mobile/firefox-ios/blob/21e9d2943...
I have met Swift teams who would have proudly refactored this outdated MVC code into a "modern" MVVM pattern, replacing the 2000 LOC controller with one 2000 LOC ViewModel and a 500 LOC controller (because you still need UIViewControllers in the Apple world).
But in my opinion the bigger issue is the insistence of only having one controller, or view model, or whatever per screen. As soon as you find a way to divide all the interconnected concerns of this screen, the layers and their names are not really that interesting.