If "performant" devices are not widespread then telemetry will reveal that the app is performing poorly for most users. If a new festure uses more memory and sugnificantly increases the crash rate, it will be disabled.
Apps are optimized for the install base, not for the engineer's own hardware.
What is the point of telemetry if your IDE launching in under 10s is considered the pinnacle of optimization?
That's like 100B+ instructions on a single core of your average superscalar CPU.
I can't wait for maps loading times being measured in percentage of trip time.
If your IDE isn’t launching instantly you have a bad IDE.
I guess so, but:
https://youtu.be/qqUgl6pFx8Q?si=x3CpsW9Aane7GHHV&t=1875
Because you don't want to regress any of the substeps of such a loading progress to turn it back into 10+ seconds of loading.