Agreed, most of the wealth generated by most businesses is enjoyed by its customers, not its owners. Take Google or Facebook - while they enjoy huge profits now, and will in the future, their profits are dwarfed by the wealth (search and connection) they have created for their users.
If synchronized clocks are a problem, I wonder why they don't race the neutrino against a photon. Obviously the photon would have to take a different path - maybe bouncing off a satellite.
I wonder how accurate the GPS synchronization is too. I'm wondering if it takes into account different atmospheric conditions and the index of refraction of radio waves in air.
How about two pairs atomic clocks. One paired at the start point, one paired at the end point then a start- and an end-clock being used in both locations? Or use a neutral third frame of reference by timing from a pulsar.
This probably wouldn't work, time dilation under gravity makes my head hurt!
>If synchronized clocks are a problem, I wonder why they don't race the neutrino against a photon. Obviously the photon would have to take a different path - maybe bouncing off a satellite.
how about just inside the fiber. How good is the ping between CERN and Gran Sasso ? :)
Just cruising around the websites of local stores in my town, their websites that were made 5-10 years ago still look the same as ever, and for the most part still function the same as ever. (The exceptions being when they relied on third-party includes that have since gone out of business.)
HTML5 is just HTML, and unless that fundamentally changes, it should work "forever." JavaScript too, again, unless you're linking to frameworks hosted by companies that later go out of business. JavaScript usually adds, but rarely takes away.
The look of your HTML site 10 years from now may look more outdated than your Flash site does, but as long as we're all still around, I'd wager that they'd both still work, provided Flash player is still a thing.
HTML5 is just HTML, and unless that fundamentally changes, it should work "forever."
That is, if you don't use the bunch of temporary CSS properties browser vendors are supporting (-moz-, -khtml-, -ms-, -o-, etc) that people often assume to be "ready" but that will be deprecated in the future.