So unbelievably disappointing, right after the disappointment of the Duo. I was in the market for both, the early reviews of the Duo stopped me from upgrading, and the landing page of this new Mac has stopped me from upgrading that.
1. No cellular? This was honestly one of the biggest selling points in my eyes. The iPhone hotspot has been so unreliable lately.
2. Never would use the touchscreen in software engineering. Agree with others that I don't understand a real use case for it, and apparently their website designers can't either.
3. OLED is nice.
4. 24h battery life is nice.
5. No M6 Pro/Max. Just getting one generation up?
6. Not even a cool name? No Macbook Ultra? Macbook Studio? Obviously not important, but even they couldn't justify it as its own separate product from the existing Pros.
On the bright side, the wallet savings are nice. Absolutely not worth a $4,150 hit (using my M4 Pro 48GB/1TB 16" as reference)
Apple said its skipping M6 for Macbook Pro -- there is no m6 pro/max -- so the next chip MBP will get is m7 in 2027. So I would hold off on buying one until next year. This is essentially a 2025 product refresh.
I remember being so excited about Cloudflare's releases that I'd check their blog every couple of weeks for what new thing they were cooking up. This was before I actually had to use them to serve production clients.
When it came time to launch (2023?), the initial setup was using DNS/Cache, Workers, Workers KV, R2, D1, Durable Objects, Access, and Queues.
My first hint was that the Typescript library to access their API was simply just wrong. API requests through the library would fail, complaining about missing fields or invalid types, even though the types said my construction was correct, and I received dismissive replies when raising it in their Discord.
Then there were the D1 issues with random requests failing.
Then there were the Durable Objects issues with syncing clients in our collaborative editor.
Then there were the KV and (by extension) Access outages.
Eventually it made sense to switch it all over to AWS. Today, I trust Cloudflare for DNS, Cache, DDoS protection, and not much else.
The "AI psychosis" that may or may not have infected Cloudflare and caused this reminds me of Github's, except Cloudflare has a much much bigger moat.
I've never understood this argument. Even if self-hosted things were offline more often (which I've never found to be the case, I've had Forgejo + runners running for a year now with no downtime), the real benefit is that you yourself can work to bring it back online when it does, rather than waiting on a large, slow-moving organization to figure out what slopped PR caused their global service serving ungodly amounts of RPS to go offline again.
Except it's not down more often and it's not a heavy lift. It's not a mail server, it's a Postgres database, a Golang app, and backups (and some providers will just handle that for you!).
Why? Like I wrote in a separate comment, it's not a mail server, it's a Postgres database, a Golang app, and backups (and some providers will just handle that for you!)
What do you mean "why"? Setting up and tinkering with systems is work I loathe to do, obviously. I want to code, not host coding repositories. I did it in the past because I had to, and now I don't have to do it because github does it for me. It's great.
Except when Github’s down, of course. I’m saying it’s incomprehensible to me that people would rather put their trust into an organization as enshittified as Microsoft where they get their codebases added to an AI, have an awful experience (the code review UX, for example), and deal with consistent downtime, rather than put a few hours every so often into something that they loathe to do. That does not seem like a good trade-off at all.
1. No cellular? This was honestly one of the biggest selling points in my eyes. The iPhone hotspot has been so unreliable lately.
2. Never would use the touchscreen in software engineering. Agree with others that I don't understand a real use case for it, and apparently their website designers can't either.
3. OLED is nice.
4. 24h battery life is nice.
5. No M6 Pro/Max. Just getting one generation up?
6. Not even a cool name? No Macbook Ultra? Macbook Studio? Obviously not important, but even they couldn't justify it as its own separate product from the existing Pros.
On the bright side, the wallet savings are nice. Absolutely not worth a $4,150 hit (using my M4 Pro 48GB/1TB 16" as reference)