Then they could give free food to countries that are experiencing short-term famine through natural or man-made disasters. In such a situation, consumers are helped and producers aren't really able to increase production in response to the high price - hence a famine.
Microsoft/Sony/Nintendo subsidize the development and cost of their dedicated gaming system from the 30% cut of the store sales.
It's very different on the mobile side: Apple sells iOS devices at full cost. With Android, it gets even more mucky as Samsung, the hardware vendor, gets 0% of the sales on their handset (unless the user, for some reason, uses the Samsung store), and Google gets the full 30% for only their software work. So the fact that Google gets 30% is wild.
> Google gets the full 30% for only their software work
Not that I trust Google (my personal phones are Apple) but how do you think a phone with all software made by Samsung will work? Every time I lay my hands on one of their phones (and I have one on my desk for Android development) something annoys me. They somehow think they know how to do UI/UX but they still haven't learned after all these years of "customizing" Android.
So yes, Google deserves some money. Not 30% but some.
So if you sell your hardware at a profit, you forfeit your right to profit off the platform post-sale? Nintendo never sells hardware at a loss either, by the way.
And your Samsung comment doesn’t make sense. Samsung gets the operating system for free and then sells hardware for whatever profit they can get for it. Plus all of the post-sale platform services profit they can manage, just like Google and Apple. What is wild?
I never meant to imply that once a company sell the hardware for profit, they forfeit the rights to profit off the platform. It's really about market power. The two dominant mobile leaders have enough market power to increase their take to 50%, for example, arguing that's how much traditional retailers take, if not for the risk of attracting government interventions.
The intention is to point out that simple arguments of 'Xbox is charging 30%, so it is fine that the mobile platforms do the same thing' failed to take into account of the nuances of the situation. Isn't it weird that these platforms are all charging 30% even through all these platforms have different business models, with different cost structure and provide different values? I hadn't even talked about how Microsoft has been getting no money off sales on Steam when it is their platform, because they hadn't (yet?) lock down the platform.
Finally, Nintendo did sell the Wii U at a loss. [0]
To get a driver signed by Microsoft, the developer of the driver is required to provide a full cert pass log from the Windows Hardware Lab Kit to dev center [0]. Do you have any article that says the CrowdStrike driver has been tested by Microsoft?
To avoid going through the full cert process the sensor was certified but it loaded code from an uncertified module too so that it could be quickly updated to catch new threats. It's a tough corner to be in, to function properly it needs to update very quickly but the cert process takes a while to complete so they went with this work around of a signed module loading uncertified code.
> My personal preference is to use time estimates with some uncertainty. A day or less. 2-3 days. A week at most.
In the project management world, there is an assumption that tasks that are overestimated and underestimated would even themselves out so that the total estimate would equal the actual time needed. Sad to say that accuracy of estimates don't follow normal distribution in software development.
I've done exactly this in the past, and then when someone asks how long the project as a whole is going to take it's easy enough to give a range. If someone says a task is going to take hours that's a range of 1-6 hours, if they say it's months that's 1-12 months. If you want more certainty in your estimate then you're going to have to give us some time to break things down.
> I clicked expecting basically an undocumented errata with specific, 100% reproducible instructions and a deep dive into the internal architecture changes that could have caused this.
That's a really high bar for a non-Intel investigation. The Pentium III 1.13GHz issue 24 years ago had 100% reproduceable instruction, but even that didn't include any deep dive into the internal architecture because that just isn't information that people have.
In BC, Canada, there is a maximum motor power limit of 500W for e-bikes. I am not sure if switching (or locking?) the e-bike to power assist level 1 would qualify.
