How do screen readers work? I’ve used all the aria- attributes to make automation/scraping hopefully more robust, but don’t have experience beyond that. Could accessibility attributes also help condense the content into something more manageable?
Won’t get you end to end latency, but should be able to trace the input events through chrome, and show the context swaps of all the Wayland/dbus stuff.
If you’re not speculatively executing, you don’t need a branch hint because you don’t need to speculate which way it goes.
Also, I don’t think executing both sides of a branch ever took off on any mainstream CPUs (unless Itanium counts). It wastes power to spend half your execution units on things that won’t be committed, why not use them on the other hyperthread instead?
Is both. They cause gravitational waves, which is how the system gets rid of energy, which allows the orbits to decay, causing the collision (and more waves).
My uninformed opinion: lots of speculative execution is good for single core performance, but terrible for power efficiency.
Have data centres always been limited by power/cooling costs, or did that only become a major consideration during the move to more commodity hardware?
The UK is not and has never been in Schengen.
I guess GP is taking about free movement of EU citizens, but that has nothing to do with Schengen.