My gut says Nintendo, because Microsoft doesn't give a shit what you use as long as you write for them, and Sony doesn't feel like they'd be that petty.
How does this work with data caps? I had to use a 4G hotspot for work for about a week and had already reached the point where I was getting throttled. Won't applications of 5G just hit this point more quickly?
Or, let's blow the carriers' minds here, they can lift the data caps and just charge you little extra for a fixed subscription, as a good chunk of Europe's carriers already do.
An executive of the carrier I use even said in an interview that it's much easier that way for them, and they are not worried that people will stream 4K video 24/7. Few years down, turns out he was right to be not worried. I can stream a 1080p Twitch gaming video just fine -- and that's in a local mall with a very polluted radio spectrum.
I think the difference here is how it functions in the music. Does the chord function as a CMaj7 in relation to the rest of the song, or does it function as an Emin6?
I think the idea is that "more capable" participants tend to make money off of "less capable" participants. And there are a lot more of the "less capable" ones.
Markets are like ecosystems, they are an emergent property of the aggregated activity of many participants. Yes, some of those participants will end up at the top of the food chain. But that's going to happen regardless of what you do.
I have a Realme GT Neo2 which comes with 128gig at about 330€.
Of course if it occupies a significant portion, it would be an issue.
On the other hand when I look at the kind of updates that Steam and Playstation are pulling, 200mb feels like nothing.
Will that 1% stop buying from Amazon, or will they just use the website instead? Gut instinct (and personal experience) says they're not really losing anything here.
Yes, I think people absolutely will buy less from Amazon if the mobile experience is just a bit slower or more annoying. We know from both other companies and Amazon's behavior that reducing friction has substantial impact on amount purchased.
I absolutely have given up on trying to buy something from them because their mobile app crashed, which is the kind of thing that could be due to them mindlessly lashing together a bunch of app frameworks rather than building something streamlines. I've also given up when trying to do something really simple like set precise price filters that are bafflingly not available on mobile.
My comment that started the sub-thread you are replying to specifically generalized the question, and I did so because I think app size, stability, and general well-built-ness are tightly connected.
> I get why smaller companies use generic janky frameworks to throw up an app quickly and keep maintenance costs down. But why doesn't Amazon have the most streamlined and elegant app on the planet? They have the resources, expertise, and scale for it to make sense to invest heavily.
Another way to say this: the root reason for app bloat is something that causes general app badness, so the question "Why is the app so bloated?" is not well explained by your implied answer "Because users do not reduce purchases on account of app size".
Fair. And for what it’s worth I would very much like for the app stores to penalize apps that are bloated. Institute a 20MB limit on the app size unless it’s a paid app or has specifically applied for a large app permission and justified why it needs more storage. That would drive developers away from bloat.
But I think large apps and apps that crash frequently is correlated but not strongly. I have never seen Amazon crash. I have seen 4MB apps crash. Bloat by itself just means I have to buy a more expensive phone to fit everything I want, which sucks but isn’t the end of the world.
I don't have amazon on my phone due to the bloat and opt to wait until I get in front of a desktop. Which means probably 80% of potential impulse buys from my phone are forgotten by the time i'm back home and they've missed out on sales. It's lost opportunity that they can't measure and so it will forever be swept under a rug.
You might be the exception here but (a) Amazon.com is accessible from your mobile phone, do you not use that? And (b) “impulse buys from my phone” is indeed hard to quantify. How do we know that you’d make any impulse buys if the app was in front of you? Going to their website on a phone is as easy if not easier than using their app and the content is identical. Yet you don’t say that you make impulse buys that way. 80% of 0 is still 0.
Again, have you ever in your life wanted to buy a product from Amazon but then didn’t because of their app size? If not, as far as Amazon is concerned you don’t care about the app size in any meaningful way.
even if they buy less because of the bloated app, you're still balancing dev resources against profit margins. It might just not be worth the effort for that extra tiny bit of revenue the app will generate by being small.
But that's my point about scale: if the revenue-vs-developer-time tradeoff makes it worth it for any company to make a good app, it will be worth it for Amazon. They are so huge that a 0.01% increase in sales translates to many millions of dollars per year.
Everything else they do also scales though. Not proportionally to each other, but I wouldn't be surprised if putting their devs on, say, better product recommendations is much more revenue than app size.
The push to get everyone on the company app will be less so. Why they want everyone on the app I don't understand but whatever those reasons are they won't benefit from it
With the top comments (now) all talking about the fact that this universal approximation theorem doesn't really have much impact in the real world. I wonder, is this interesting outside of theory? Has this motivated any techniques that have created (or may create) real-world, empirical results? Could it even?
Plenty of problems in the area of computation have little impact on the real world, but they contribute to our fundamental understanding of ‘understanding’. The Entscheidungsproblem is probably the most significant of these.
I'd love to have the ability to write a direct query plan, for the rare occasion where the query planner does something stupid. But, ya SQL is great for the majority of situations.
