These obviously are’t planned obsolescence though.
Flexgate is a manufacturing error, that they handled in a consumer hostile way
Batterygate, was an arguably misguided way to support outdated models - prioritising one goal (battery life) over another (speed)
The iPod thing I’ll admit I know nothing about.
It sounds like, for you, planned obsolescence is defined as any instance where a product isn’t manufactured perfectly or degardes over time, regardless of whether it was planned. For me, planned obsolescence should contain at least a hint of planning.
Your interpretation of my comment, though I guess intended as a joke, can only really mean two things:
1. You are unaware of DHH’s more recent favoured topics
2. You don’t think there is a problem with DHH’s opinions
Either is fine, I don’t really care.
The issue for me is that Cloudflare’s PR team obviously are aware what DHH writes about. And they’re sponsoring his project anyway. Cloudflare knows that this is repellant to a lot of people, that some of us will begin removing them from our stacks in response. But they don’t care, because they think it’s more valuable to cosy up to a bunch of mid life crises who’ve spent too much time on twitter.
Thanks for the response, and apologies for misrepresenting your results somewhat! I'm probably not going to change the title since I am at heart and polemicist and a sloppy thinker, but I'll update the article to call out this misrepresentation.
That said, I think that what I wrote more or less encompasses three of the factors you call out as being likely to contribute: "High developer familiarity with reposito-
ries", "Large and complex repositories", and "Implicit repository context".
I thought more about experimenting on myself, and while I hope to do it - I think it will be very hard to create a controlled enviornment whilst also responding to the demands the job puts on me. I also don't have the luxury of a list of well scoped tasks that could feasibly be completed in a few hours.
In case anyone isn't familiar with remix, bloomingkales seemingly has no familiarity with the framework. Obviously it's not been created as a conspiracy to sell training courses. The idea is ludicrous.
It's quite a nice framework. It's easy to learn, straightforward, the people in their discord are very helpful. It has the backing of a large company (shopify) who are using it extensively.
It is, I'll say again, obviously not a conspiracy to sell training courses.
I do think this is a cool product, but I would be very hesitant to buy a clock that relies on the internet, and on an API that might die at some point.