7 ms·
but the use is massively frustrating. Swipe controls don't work, the app sucks, pairing with multiple devices is a nightmare. This is a great express
by wcarss 6y ago
but the use is massively frustrating. Swipe controls
don't work, the app sucks, pairing with multiple devices
is a nightmare.
This is a great expression of one of the primary issues facing the software (and technology) industry today: it seems like software is fundamentally just too hard to do right. Basic competency and non-broken operation is regarded as a hugely valuable luxury feature. It's a cornerstone of the luxury technology brand!
But... is software really too hard? If so, how does Apple do it, are they just better engineers than the people who work at Sony? Maybe, but that seems unlikely to account for the difference.
And of course I don't really know, as I'm just a person on the internet, but I have a hunch: I believe Apple can do better because they have so much vertical integration, i.e. real control over much more of the technology stack in their product.
Let's say Sony has some in-house devs, but they hire a team on contract for the app's actual UI. Sony's just going to write the API layer for the UI to talk to. Sony will also make some of the hardware, but they're using a prefab chip and some antenna they bought, and they'll buy some proprietary off-the-shelf firmware for the lowest layer.
But, maybe it turns out the antenna and the chip don't play nicely under some key modes of operation. They can't redesign either of them, because they're just buying those parts. They shop around changes, but it would exceed reasonable costs. Maybe the firmware should be able to compensate here, but it's closed-source, and the company that wrote it shut down and sold their properties to someone else that won't turn any request around in under a year. And then, Sony sells the division that was working on the API, and they end up finishing the job out as a contract. This leaves all the API<->UI planning to contractors talking through an intermediary who still works at Sony. So it goes. And we all end up with another expensive piece of crap that just doesn't work.
But on Apple's side? I bet way more of it is in-house, and what isn't is locked in on deals that make Apple by far the most important customer. If they need a change, they get it. Apple's teams just... write the software that needs to get written! Maybe they physically meet each other. The firmware gets fixed when it's needed. And Apple ends up with a 'luxury product' built atop "hey look, it actually works!"
Is my point that everyone should be like Apple, or SpaceX? It's clear that not every firm can have tight vertical integration. Most have nowhere near the size, power, time, or budget to do this.
So my point is that if software and hardware were open by default, at least we could fix the damn things.
Sony maybe made some decent hardware there. It need not be shackled to some crayola software joke, if only they (and all of us) weren't so darn proud of our intellectual property that we could never dream of allowing someone to take a wrench to it.
Things being closed is so built-in that it's hard to even imagine this: how would we fix the headphone software? We'd probably need (expensive, hard to use) ROM-flashing utility hardware, decompilers, and the ability to load arbitrary code onto Apple devices! Impossible! Well, it's all hard because we want it that way. It's safer, probably.
But it boggles the mind.
- _jal 6y ago> I believe Apple can do better because they have so much vertical integration That is a big part of it. But how did Apple do well enough to vertically integrate? They were not the crazy powerhouse they are now for most of their history. Another big aspect is culture. Apple chooses not to ship things they don't think are good enough. Put aside that they're not always correct. How many other shops do that? How many places stick to the schedule relentlessly, because shipping is all that matters to them? Convince themselves they'll fix the software problems after release? A big part, I think, is a combination of knowing when it is 'good enough', combined with the courage, patience and money to keep building until you get there (or spike the project because you missed the market window).
- brightrhino 6y agoDidn't Apple start integrated? The Apple 1 and Apple II were largely designed by them, the OS was written by Apple, they licensed Basic from Microsoft. The Integrated Woz Machine [0] ran the floppy drive. It seems like it's part of their DNA, they always try to do as much as possible themselves. [0] https://en.wikipedia.org/wiki/Integrated_Woz_Machine https://en.wikipedia.org/wiki/Integrated_Woz_Machine
- jacquesm 6y agoNo, those were tinkerers machines with as much of their IO exposed as could be done. Even the later Lisa had expansion slots.
- nobleach 6y agoThere's a simple reason. From the top down, the culture at Sony is, "it's good enough for 90%". And getting that extra 10% isn't going to be worth the investment. Those folks can go buy Apple. I have dealt with SO many (and worked for some) software companies that live by this axiom. Get an MVP to market, who cares if its riddled with bugs and hobbles along with duct-tape and paperclips holding it together. "We're just going to throw it away and rewrite it later". Devs spend all their days fixing little bugs with more band-aids - dreaming of the day when they can re-arch it properly. But the truth is, that day is never coming. Why? Because think of the expense vs the gain. It literally is not worth it to have a better experience. The crappy version is already making money. Customer Service agents are cheap. Achieving Apple-level polish is simply not worth it to most companies. That's why you have Chrysler mini-vans dying after 5 years vs Honda mini-vans lasting 15 years.