Prosperous for whom? You and the other exiles you surrounded yourself with? Guessing they were a fairly monochromatic bunch too, huh?
Batista was a violent, corrupt dictator. My grandmother lived in Cuba during those days in absolute poverty. It's not wise to talk in absolutes, your family was prosperous but most Cubans were not.
Domestically there was Anwar al-Awlaki who was a US citizen who proselytised against the USA. His 16 year old nephew who was also a citizen was killed as well, despite no known involvement.
To be fair, earlier in the year the administration promised to implement additional safeguards and oversight for these programmes, but brass tacks a progressive administration killed US citizens in non-war zones because of an executive decision with no due process.
Good enough for what? I used the first build of WebVR with my DK2 on 2013 Macbook Pro and tried a simple Quake level viewer. Sure, no AAA graphics but it worked, and well!
The new drivers removed my ability to experiment with WebVR. I could no longer use the hardware not due to limitations with my computer, but limitations imposed for marketing purposes.
The module checks that the positive integer is less than Number.MAX_SAFE_INTEGER constant, while yours would lead to unsafe comparisons if we trust its validity as a number.
The name of the function, though, isn’t `isPositiveSafeInteger`; it matches `Number.isInteger` instead.
Or maybe you don’t just want safe integers, maybe you want `x >>> 0 === x`, or `x > 0 && (x | 0) === x`, or…. This is what I meant about JavaScript being confused about the definition of “integer”.
What about the other 50% of Android users that don't have Chrome or Chrome WebView? I've been working mobile for a few years now and would love to drop anything before KitKat, but that's not something feasible given market share.
In practice, pre 4.4 embedded WebViews have worse support for standards than Mobile Safari. Chrome for Android was in part a system component in order to replace 4.4's embedded WebView, only until 5.0+ did it become decoupled.[1]
Google's evergreen approach reduces fragmentation of a core API and it's been a godsend. I know in the future, Safari will be left alone as a pain point. Just don't misrepresent the present situation, where older Android has worse standards support than Mobile Safari and can't even be debugged in devtools.
> "pre 4.4 embedded WebViews have worse support for standards than Mobile Safari"
My old Windows XP box also has worse support for standards than Mobile Safari.
OK, so XP also doesn't have market share. But it's hard to blame older versions of Android for not supporting standards that didn't exist when they were implemented, just because people continue to buy low-end devices running those old versions.
Right, but at the same time you can't say that Safari is the only thing holding mobile web development back. Because dropping users on "old" versions of Android isn't an option from a business standpoint, Safari isn't the only thing holding people back. And 4.4 really isn't that old; so there are tons of users on older devices.
The Android browser was a sore joke and didn't support years old standards. It was embarrassing for Google, the top web company, to release a browser that was so impaired and so slow at adopting standards, years after Mobile Safari. With Chrome, google has reverted the situation and they are now bleeding edge.
Android Chrome has about 13.3% global usage, and all versions of Android Browser have about 6.5%. If we do not count versions before 4.4, then Android Browser has about 2.5%.
Also worth pointing out that Chrome for Android is over the 1 billion mark (1,000,000,000 - 5,000,000,000)
Batista was a violent, corrupt dictator. My grandmother lived in Cuba during those days in absolute poverty. It's not wise to talk in absolutes, your family was prosperous but most Cubans were not.