Well the battery is usually glued, but Apple has started using this weird glue that releases if you give it a specific electric charge. It's replaceable but it's a complicated affair. I expect the Neo's battery to be glued on the chassis.
The SSD is difficult to replace because Apple uses storage chips with no controller; the SSD controller is in their CPU. So you can't put in any M.2 in there even if you wanted. Some small companies have managed to offer upgrade parts for the Mac Mini, which has socketed storage chips.
As time marches on and PC manufacturers stay still, Apple manages to simplify its logic boards by reducing the number of connectors and parts, lowering the price to make a computer. Apple, which has never really offered anything below 1000$, has entered a new market with a bang.
I expect a computer in 20 years to look like the system-on-a-chip that Apple makes for its watches. I don't know why people are adamant that we need more controllers and chips on our machines, not less.
A few weeks ago Apple had a tiny (<10MB) update for media codecs ready to install on my MBP. I expanded the details for that software update and saw that if I had run it, it would also have downloaded and installed Tahoe. Apple is burning so much trust right now with these dark patterns.
Definitely going to give this a try. One thing I'm curious about--where are the servers? And if I want to choose hosting geographically close to me, how do I do that?
How much is “the public” making? The title of the post says millions. The title of the article says trillions. The second paragraph of the article says not trillions. Sheesh
I love squoosh! It’s been one of the few PWAs I have installed and actually use regularly.
Does anyone know if their optimization methods still best-in-class these days? It’s been good enough for all my practical needs, but I know it’s been around for a while and there may be better techniques for some file types now.
Love this! Just wanted to note that I think there’s a mistake on the flyweight pattern page’s example. You’re using getting a boolean with Set.has but treating it like a Book (as if you had used Set.get). I also don’t really understand how this saves memory if you’re spreading the result into a new object, but maybe someone here can enlighten me!
Ah I think I understand now. The return type of createBook is true | Book, which is likely a mistake, but happens to work because when you attempt to spread a boolean into an object it removes itself. But if you were to edit the example to have a stable return type of Book then it would no longer save memory, so perhaps that was intentional?
I’m surprised by how good it looks. This is really cool! I do feel like the Q and 4 characters need a little manual tweaking since the blur+threshold technique leaves some artifacts in the corners but those are such minor issues given how readable this font is overall. Love it.
reply