I think what you might be overlooking, at least from the point of why they would require it, is that there are just a lot less people in Canada. Their population is around 15% that of the USA. Even if a large portion of their population was interested, it would be harder to drive the numbers needed.

It's not non-compliance if a stay has been issued during the appeal process. This is how the courts work, for better or worse. The injunction also allows for Google, or Epic, to request modification for good cause. Further, there is nothing say that a more permanent injunction couldn't/wouldn't be applied later. I don't think a temporary injunction was meant to permanently resolve things in the first place.

And?

This is a civil case. There are rules around whether an order is stayed during the appeal process. I would assume this happened within those rules.

2024 to 2027 looks like three years to me. It can suck sometimes, but the appeal process does exist for good reason.

Others have noted that the fee to the customer and the fee to the restaurant are separate. However, what I don't see mentioned is that many/most restaurants raise the price of the food on the delivery apps. As far as I understand it, the pricing on the apps is controlled by the restaurant. An easy to look up example is McDonald's. Their food is about 15-20% more in app. I wouldn't be surprised if they negotiated lower fees, but even if they didn't the customer is still paying around half of that 30%.

This might differ for non-partner restaurants, but I know the delivery fees to the customer are higher in those cases.

They already have, to an extent. You can run many iPhone/iPad apps and widgets on the newer Macs. The UI on MacOS has also looked like it's been skewing towards touch for a while.

I can only speak to myself. I don't use a laptop too frequently, desktop is primary, but I'd say a touch screen is/would be useful about 30-50% of the time while on it. I often find myself wanting to just tap on things, with Windows and MacOS. It's usually limited to casual usage.

While I wouldn't assume touch is the primary desired method of interaction, I know there can be times where it would be easier, or more intuitive, than using the touchpad. Further, with Apple integrating iPad apps and widgets into MacOS it seems at least somewhat more likely to be useful/desirable. From a function standpoint, it's a feature that cannot easily be handled via aftermarket. As such, it's generally better to have the option for those that need/want it. The only real reason to keep it out is cost.

I think they were saying a reasonable minimum required cloud support period should be 2 years per $100 of the device's cost.

Apple doesn't produce their displays, flexible or otherwise.

With a reported 320+ million daily users, I would imagine there would have to be at least some CPU usage on those servers.

Peak load is going to be a concern, regardless of code optimization. The peak load problem is one based on human factors, not software. All optimization would change is the scale. That is, you'd still have the same concern just with potentially fewer servers overall. It might affect the cost/benefit of the work, but that is it.

The alternative to dynamic overclocking is to have more, or more powerful, servers to handle the peak load. This problem exists regardless of how (un)optimized you believe their code to be.

I had a similar thought. I appreciate when both system are included, as it usually saves me time getting an exact conversion if I care, but that obviously isn't the way to do it.

The first source I found, cannot vouch for 100% accuracy.

https://www.citizensadvice.org...