This essentially turns it into a very shiny paperweight.
So is Apple's anti-theft security a wonderful boon to users?
Or is it just another evil corporation strengthening it's monopoly power?
This essentially turns it into a very shiny paperweight.
My how the corporate overlords have trained us to be their apologists.
Unfortunately I hadn't read up enough to be an expert on their T2 chip and Activation lock.
But there's a lot of assuming happening there.
Ah but the buyer should beware, right?
Maybe. We'll assume yes now for the sake of argument.
Great. Why does Apple care?
That'd be a MUCH bigger profit incentive for Apple than merely cracking down on stolen computers
Any buyer who knows about this is going to be VERY worried about buying a used computer. Apple has effectively drastically reduced the used computer market for their computers.
Which costs money.
AND you have to have the ORIGINAL proof of purchase.
This may provide me with recourse, because I have the expertise to do it (though it's unclear if I have the patience — I may just get my money back from ebay).
People who steal computers.
It is Apple's administration of this new technology that is monopolist and outrageous.
More from Tech
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.