>>When you're limited to a single language, what you end up with is a software engineering monoculture.
If you want monoculture, look at Ruby. (Don't get me wrong, I love Ruby and it's my favorite language, but it's basically dominated by the monoculture of Rails.)
I think you guys are using the word monoculture to mean different things but you share a common worry.
_frog is worried by a language monoculture, having to develop for a platform in only one language: the platform mandates the language. Other examples: Java for Android, Objective-C for iOS (Swift now).
Being able to program the web in many different languages would be both good (pick the tool you like most) and bad (example: "sorry, I can't take over this webapp because it's written in OCaml and I only do Ruby and Elixir, find somebody who knows OCaml") but not different from what we always did when developing for the desktop and the web server. Both did well. If we're heading there we'll cope with that (customers will stick with the "big" languages, as usual).
Are you talking about the thing where going fullscreen places the video in a new virtual desktop? Because if that's the case I vastly prefer that behaviour. It makes it much easier to jump back and forth between watching a fullscreen video and reading content in other browser tabs.
I actually distinctly remember getting a copy of Metal Gear Solid 2 and being confused why I couldn't start the game. Hitting any button on the splash screen would take you to the menu, and then hitting X from there would take you back to the splash screen. Having primarily played western games up to that point, it didn't even occur to me that another button could be used for 'confirm'.
It seems like Sony, being a Japanese company, originally intended for O to represent yes, and X to represent no. If you look at a lot of early PlayStation games, or most modern games released in Japan, that convention is apparent. The O and X buttons on the PlayStation controller even match the placement of A and B buttons on Nintendo's controllers, providing a clear analogue between the two.
I'd be curious to know what caused that convention to change in the west.
The XBox controller is a clone of the Dreamcast controller. If you go back even further to the Megadrive, it had 6 buttons (on advanced controllers) with two rows of buttons - xyz and ABC arrayed from left to right.
When the Playstation 1 was released, the two consoles consumers could have been familiar with in the west were Super Nintendo and Sega Megadrive. SNES had the familiar ABXY, but mirrored with AX on the right. It used A for yes and B for no. The Megadrive had the aforementioned ABCxyz and also used A for yes and B for no. Meaning, one console used the bottom button for yes and the one on its right for no (Megadrive), while the other had the bottom button for no and the one on the right for yes (SNES).
So I doubt SONY copied the competition for their decision to swap the yes/no buttons.
I've had luck installing most Ruby gems used by my projects. The only exception so far has been Nokogiri, and even in that case there were instructions on the project's web page that got it to install without a hitch.
There seems to be a fundamental misunderstanding here about what Apple's HealthKit is. HealthKit is simply the name for the API framework Apple is making available to developers, following in the naming conventions of UIKit, WebKit, SpriteKit and so on.
HealthKit is not, however, a name that consumers will ever actually come across in using their device. Apple's own app on top of HealthKit is simply called "Health", and I highly doubt the string "HealthKit" appears anywhere in that app's UI.
It's a huge distinction if formal legal action happens because Apple can establish quite easily that they have relied on the Kit format for previous software, whereas HealthKit.com doesn't (AFAIK) have any major traction in the software space. Law student here, IANAL, so take this with a huge grain of salt.
Either way, in Australia, both parties would apply under Classes 9 and 44 which covers all computer software and medical services respectively. It's likely that Apple will win on class 9 as "Kit" is far better known in the software community than "HealthKit.com"; and arguably 44 too, depending on Healthkit.com's traction in the medical field.
It's unlikely that Apple's HealthKit and HealthKit's HealthKit would cause confusion in the market - but it makes a silly story to say that Apple's Health (which may have overlapping functionality with the preexisting HealthKit).
And regardless, there's unlikely to be overlap between the markets for these two products. HealthKit.com is somewhat hard to navigate, but the impression I get is that their product is aimed at medical practitioners. I doubt they overlap with the mobile developer demographic to any significant extent.
Though I'm curious to hear from someone with more legal knowledge than me: would the fact that there's very little chance of collision between these names protect either party from legal repercussions?
What about the effect of search engines on brand value? Whereas, before, the existing HealthKit was probably the top result, after an invasion of Apple HealthKit development sites they may be kicked to the third page hellban.
Naturally, this same reasoning can be used to challenge the use of the same trademark in a different domain, something clearly accepted by law.
The fact that has Apple has more money than they know what to do with is the real factor for legal repercussions.
It's one thing to have theoretically defensible IP, and other thing entirely to actually be able to.
Assuming equal resources backing the legal teams, it would probably be sufficient that they are both forms of software, as all software trademarks are lumped together in the single category. There might be some sort of passing off action one way or another but it would be more likely to come from Apple than HealthKit.
There seems to be overlap between the Health app and Healthkit.com which I suppose is the real issue. Hard to tell if Healthkit truly got sherlocked though, because I can't tell what they do from their website past management software.