armistace/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

apple_the_anti_dev_platform #19

Merged
armistace merged 11 commits from apple_the_anti_dev_platform into master 2025-08-28 14:33:29 +10:00
Conversation 0 Commits 11 Files Changed 1 +62 -21
1 changed files with 62 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit f14eb6d30c - Show all commits

83
src/content/apple_the_anti_dev_platform.md
View File

@ -1,41 +1,82 @@
# Apple: The Anti-Dev Platform
# Apple. The anti dev platform.
## A Recent Trial
## The Great Mac‑Mishap of the Week
This week has been quite the adventure. I found myself wrestling with MacOS at my day job. It has helped reinforce my existing disdain of the platform, in fact, in the 10ish years since I have used an Apple based platform I can safely say one thing. It got worse.
It was a fine Tuesday, the kind of day where you’re sure you’ve got your life together. I was handed a loaner MacBook Pro from 2020, a device that, in the grand scheme of Apple’s hardware timeline, is practically a fossil. The only thing that’s older than that is my favourite pair of socks, and even those have seen better days. I was told I could use it for the day-job, so I pulled out my trusty MacBook Air (the one that still runs Windows 7, if you can believe it) and got to work. Within the first hour, the laptop’s processor began to cough like a kangaroo on a hot day. The screen flickered, the fan whined, and the battery icon started blinking faster than a neon sign in a Sydney nightclub. I thought, “Sure thing, this is just a bit of lag.” Then I realised I needed Xcode. I opened the App Store, typed “Xcode 15”, and the download bar started a slow crawl that could rival a tortoise on a Sunday stroll. My MacBook Pro just wasn’t up to the task. It was like trying to run a marathon in a pair of flip-flops. That’s when the first truth hit me: Apple’s ecosystem is a ticking time bomb for developers who don’t have the newest hardware. And that’s just the tip of the iceberg.
## The Loaned Device & Forced Upgrades
## Hardware Hiccups: The “New‑Hardware‑Only” Doctrine
My loan device was from 2020, apparently too ancient to run the latest macOS. I needed Xcode, and naturally, if I can't run the latest macOS, I can't run the latest Xcode. The takeaway? To use the newest development tools on a Mac, you need hardware that's fresh out of the factory. This is ridiculous.
Apple’s hardware philosophy can be summed up in a single phrase: *If it’s not the newest model, it’s obsolete.* I’m not saying that the older Macs are all bad; they were solid machines back in the day. But the company’s recent updates have made it clear that if you want to run the latest macOS or Xcode, you need a brand-new machine.
It feels like Apple is pushing users towards constant upgrades, mirroring Microsoft’s move with Windows 11 and its TPM 2.0 requirement. Both practices feel like forced obsolescence, encouraging unnecessary hardware upgrades and contributing to electronic waste.
* **Latest macOS**: Requires a 2017-era MacBook Pro or newer.
* **Latest Xcode**: Requires macOS 13 or newer.
* **Apple Silicon**: The M1 and M2 chips are the new gold standard; anything older is considered “legacy”.
## Developer Realities: A False Economy
This isn’t just a policy; it’s a marketing strategy. Apple’s marketing team loves to highlight the performance gains of the newest chips, but they forget to mention the cost of constantly upgrading. The result? Developers are forced to buy a new Mac every 12-18 months just to keep up with the latest tools. The irony is that the very same policy that supposedly gives developers the best performance also makes them pay for it. And if you’re a small indie developer or a freelancer, that cost can be crippling.
Most developers today only need a device to write code and push to remote pipelines. So, the idea that a machine becomes "obsolete" after five years is absurd. I use a 15-year-old machine with an 8-year-old graphics card for gaming and AI workloads. I have a 4-year-old rig as my main gaming computer. These machines run Linux swimmingly. Why can’t Apple be more flexible?
## Software Snags: Xcode, macOS, and the Never‑Ending Update Cycle
This creates a false economy. To develop on Apple, you basically have a $2k to $3k AUD cost every year on top of the $150 AUD entrance fee to be an Apple developer.
The software side of the Apple ecosystem is just as unforgiving. Here’s a quick rundown of the pain points:
## The Cost of Entry
| Issue | What Happens | Why It Matters |
| :------------------------ | :----------------------------------------- | :------------------------------------------- |
| **Xcode Compatibility** | Older macOS versions can’t run the latest Xcode. | You can’t build new iOS apps or use the latest Swift features. |
| **macOS Updates** | Must run the latest macOS to get the newest Xcode. | Each macOS update often requires a new hardware generation. |
| **App Store Policies** | Newer apps require newer SDKs. | Your app may be rejected for not meeting minimum requirements. |
The financial burden of being an Apple developer is substantial. The $150 annual fee, coupled with the high cost of Mac hardware, creates a significant barrier for many developers, especially newcomers. This exclusivity is problematic and counterproductive to fostering a diverse development community.
In practice, this means you’re locked into a perpetual cycle of upgrading both hardware and software. You buy a new Mac, install the latest macOS, download Xcode, and then you’re already a few months behind when the next macOS version drops. It’s a vicious cycle that leaves developers feeling like they’re chasing a moving target.
## Security as Control
## Forced Obsolescence: A Modern‑Day Car‑Replacement Policy
Arguments about security as a defense for Apple’s practices are disingenuous. If you’re using cloud services, you’re already compromised. Apple uses security as an excuse to control their ecosystem tightly, which isn’t helpful for developers or consumers.
Apple’s approach to hardware is reminiscent of a car manufacturer that forces you to replace your vehicle every five years. Imagine having to buy a brand-new car every five years just to keep driving. It’s absurd, isn’t it? Well, that’s essentially what Apple is doing, but with laptops. Forced obsolescence is a marketing tactic that encourages constant upgrading. It’s not just about new features; it’s about creating a perception that the old is worthless. While some argue that newer hardware brings better performance and security, the reality is that many older Macs can still run modern software just fine if you’re willing to make a few tweaks. Consider the following:
## Loss of Control & Identity Verification
* **Linux on old Macs**: Many developers install Linux on older Macs to extend their life.
* **Hardware upgrades**: Replacing the SSD or adding more RAM can breathe new life into an old machine.
* **Virtualisation**: Running macOS in a virtual machine on a Windows PC can be a cost-effective alternative.
The cumbersome process of signing in and enrolling everywhere to build apps feels like a loss of control over your devices. If you purchase an Apple product, shouldn’t you have the freedom to use it without excessive restrictions? And the requirement to upload government-issued IDs for their developer accounts? It makes me question Apple’s priorities.
Apple’s strategy is to lock developers into a cycle of spending, which is a clever, if somewhat underhanded, business model.
## The Wider Impact on Consumers
## The Cost of Being an Apple Developer
The issues aren’t confined to developers; consumers also bear the brunt of Apple’s policies. Higher costs and reduced control over devices make Apple products less appealing for those who value freedom and flexibility in their tech choices.
Let’s talk numbers. If you’re a developer who wants to publish on the App Store, you’re looking at:
## A Call to Action
* **Apple Developer Program**: $99 AUD per year (or $150 USD).
* **Hardware**: $2,000–$3,000 AUD for a new MacBook Pro.
* **Software**: Free, but you need the latest macOS to run Xcode.
* **Other Costs**: Cloud build services, testing devices, and so on.
I urge developers to recognize these anti-consumer practices and advocate for change. In future roles, I will advocate for an “Apple tax” – think $5k for new equipment and 25% extra per hour wasted navigating these unnecessary hurdles.
That’s a lot of money for a hobbyist or a small indie studio. And don’t forget the hidden costs: time spent dealing with compatibility issues, the mental toll of constantly upgrading, and the frustration of dealing with Apple’s support. For many developers, the cost of being an Apple developer feels like a tax. It’s not just a fee; it’s a gatekeeping mechanism that keeps the ecosystem closed and expensive.
## Conclusion
## Security Myths vs. Reality
Apple’s approach is undeniably anti-consumer and anti-user. They need to reassess their strategies to avoid alienating those who value open technology and flexibility. Until then, the tech community should remain vigilant and vocal about these issues.
Apple’s marketing often touts security as a selling point. “Your data is safe because you’re in the Apple ecosystem.” But the reality is that security is a shared responsibility. Here’s why:
* **Cloud Services**: If you’re using a cloud build service, your code is already in the cloud.
* **Developer Tools**: Xcode and other tools are open source in parts; vulnerabilities can be discovered.
* **Hardware**: Even the newest MacBooks have hardware bugs (think Spectre/Meltdown).
The real question is: does the extra cost of an Apple device justify the security benefits? For many developers, the answer is no. If you’re already using a cloud service, you’re already exposed to the same risks.
## Linux to the Rescue: My 15‑Year‑Old Beast
I’ve had a 15-year-old desktop that still runs Linux with flying colours. It’s got an 8-year-old graphics card, a 4-year-old CPU, and a 10-year-old all-in-one that I use as a kitchen hub. Here’s what it can do:
* **Latest AI tools**: Runs the newest AI frameworks, albeit a bit slower.
* **Gaming**: Handles most modern games at decent settings.
* **Development**: Works for web development, Python, and even some C++ projects.
All of this without spending a fortune on new hardware. The only downside is that I can’t run Xcode or build iOS apps. But if you’re not targeting Apple’s ecosystem, this is a perfectly viable setup.
## The “Apple Tax” and the Future of Development
I’m not just ranting for the sake of it. I’m advocating for change. If Apple wants to keep developers happy, they need to:
1. **Lower the entry cost**: Reduce or eliminate the developer program fee.
2. **Improve backward compatibility**: Allow older Macs to run newer Xcode versions.
3. **Offer better support for non‑Apple platforms**: Provide tools for building iOS apps on Linux or Windows.
Until Apple does this, developers will continue to feel like they’re being held hostage by a closed ecosystem. The solution? Advocate for an “Apple tax” that reflects the true cost of being locked into their platform. Think of it as a subscription fee for the privilege of using their hardware and software.
## Conclusion: Time to Re‑think the Ecosystem
In the end, the Apple ecosystem feels like a trap for developers. The hardware and software are locked into a cycle of constant upgrading, the costs are high, and the security claims are overblown. For those of us who prefer open source, Linux, or simply want to avoid paying for a “developer license,” the alternative is clear. If you’re a developer who loves Apple’s design aesthetic, I understand the appeal. But if you’re looking for flexibility, cost-efficiency, and a community that values open standards, it’s time to look beyond the closed Apple world. Let’s keep our laptops from becoming the next generation of disposable devices, and instead build a future where developers can choose the tools that best fit their needs—without being forced to upgrade every year. Thanks for sticking with me through this rant. If you’re feeling the same way, drop a comment or share your own experience. Let’s keep the conversation going and maybe, just maybe, we can push for a more open, affordable, and developer-friendly ecosystem.