You might be interested in https://github.com/koush/electron-chrome - as the developer stated he was polyfilling all the chrome.* APIs and replicating the Chrome App environment in Electron and was open sourcing it in case anyone else wants to keep running Chrome apps.
Gee. Google code not working on non-google browsers. What a surprise.
Speaking as a firefox user, I'm lucky if google docs even loads, let alone works properly. Yet a another example of google talking out of their ass about "supporting web standards"
What are you gaining by replacing the native scroll functionality?
Are you trying to add "standard Android scrolling inertia" or something? I mean you must be trying to change something, or will I not notice it when it's working?
We currently can’t scroll on the body element due to a limitation in Chrome, where an empty body layer is not being optimized. So we are scrolling in an element. However, that usually requires setting `-webkit-overflow-scrolling: touch;` so that you can scroll as usual on iOS. However, that in turn has a lot of hidden implications (like squashing layers, etc. Don’t know the details right now), that make performance suffer greatly.
AFAIK, Safari will change their scroll-on-element behavior. Let’s see what the future brings.
Yeah, and memory is infinite, and all disks are free, and the computing fairies make all the processors super fast.
But back in the real world, startup time is a valid concern.
If your services consistently restart quickly, it gives you the freedom to design things differently.
E.g. doing a rolling update across a large number of instances by restarting a service at a time can become a quick enough process to be viable in instances where you'd otherwise need lots of excess capacity to be able to cycle larger proportions of instances at the same time. Making full rolling updates "cheaper" both in time and resources also translates to making rapid updates a safer choice (e.g. if I can roll back a broken release in 5 minutes, it's far safer to push out a new release than if a rollback takes hours).
That just means you expect restarting to be slow and have excluded it from your system design.
There is no problem with restarting nginx to update its config once a second, and it's even encouraged that you do so. Besides, crash-only software recovery is really the only morally sound development technique.
Worst cables ever... so far for the 'superior' hardware.
Prices are at their fairest the moment they release new hardware. The later you buy their hardware the bigger the difference with their competitors (They only lower the price of older hardware when releasing a new model and not that much either).
But superior hardware, no, that is a bridge too far. Decent hardware, yes, but not all hardware from Apple is equal.
