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)

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 was expecting, at the very least, to see Apple make their App Store 18+ checks available to developers at WWDC this year. Yet, there's still nothing except the self-reported (useless) "Declared Age Range." Apple has the best integration story of all of them, and could bring it to their entire ecosystem (native iOS apps, mobile Safari, all of MacOS), yet they haven't. Why?

Also, nothing comes to mind regarding browsers, android devices, or non-mobile devices. As far as I'm aware, no one seems to be in a rush to make this available. With non-Apple hardware, I can see it being trickier, but still, I haven't seen many (any) attempts. Why?

It probably doesn't help that many don't see the difference between "deep-state surveillance digital ID verification" and privacy-preserving ZKPs to verify age.

- The OS Redesign

- "Sexy Legal Documents"

- Emails with "" as the subject line

- Having a merch shop with action figures of your CEO

It works both ways. When you're looking for adoption and making very pro-user moves, I guess it can be a benefit. However, when you're now looking to grow revenue and making very anti-user moves, it's insult to injury.

I'm the last person to say that tech "shouldn't be fun" or something overly-broad like that, but if your messaging doesn't match the decisions of leadership, you're gonna have a bad time.

I remember people cheering about their "OS" web redesign, which was the most confusing and unnecessary UX complication when I needed to go track down a session replay to debug something (They've since added navigation to the top right.)

Like when you think of the App/Play store lockdowns, the new ReCaptcha attestation stuff, and other things that have a more authoritarian angle to it as of late, you can at least see how it happens: most of their consumers aren't technical and don't even know how to argue against it or why they should care.

With Bambu on the other hand, I'd think a good portion of its customers do actively care about this kind of thing. 3D printing just doesn't have the same market reach as computers and smartphones.

Also, it seems to me like there's eventually going to be a turning of the tide on all of these pushes (app stores included) and companies that are making these kinds of moves aren't seeing that writing on the wall.

Anyways, yeah, my next purchase will be a Prusa.

Businesses will do what businesses will do, but it seems to me having something to point to and saying "do this instead" is more effective than "this sucks and isn't even about security, don't do this at all" even though it's true.

For example, https://imgur.com/a/ia2GCgg -- top is VSCode, bottom is Zed. Both using Svelte, and using a similar theme.

- Angle brackets are a different color

- Capitalized built-in components are a different color

- Boolean props are a different color

- Brackets are colored differently than text.

The inspector is a game changer, clicking into these specific things in the preview they provide is super helpful.

- pretended that it wasn't all about invading peoples' privacy.

- done a good ol' fashioned "but Apple does it"

- pretended to be standards-oriented

- advertised it as something completely transparent to the end-user

Seems like that would've caused a lot less backlash while still achieving the goal of having some form of device attestation -- but I'm guessing that's not the real goal.