Hacker News new | ask | show | jobs
by MobileVet 2545 days ago
Seriously. Considering what a cluster the spec is and the budgetary goals for a project like the Pi, this feels really harsh. The focus is on the mistake and how trivial it was without any thought of why or how.

Pointing out mistakes can be done without being such a jerk about it.

3 comments

They spend months if not years on the design and crank out millions. Getting USB-C right seems like a no-brainer!
I highly doubt they spent years on the design... But regardless we all make mistakes.

What is a no brainer to you may not be to everyone.

Besides, you are fundamentally assuming this was a mistake and not a deliberate design decision. Maybe they prioritized X over following the spec 100%. I may not make that decision, but that doesn’t mean they didn’t.

This is exactly why the presence of this mistake appears very careless.

When you are met with a complicated spec with known issues, do you test more or less? I know which I'd pick, and if they had tested common cables like those from Google or Apple (I'm sure someone has a macbook), they'd see it not work.

The spec might be bad but then why deviate from The Reference implementation without thorough review and testing!?