Yup, and not even with desktop / mobile OSes. Generally it's the other way around. Where the users go, developers will follow.
There are cases where the relationship is important, like in the early stages of a product - where in some scenarios you need both. And yes, if you need developers, and developing for platform x is hard, and y is easy - all else being equal y would win.
Often the reason can also be evolution. Where the code started off doing something specific - but then as it evolved, more features were added, approaches changed, the code evolved to do something totally different.
Also "starters" - people who are good with getting something shippable fast and iterating on features and not the same people as the ones that write truly great code - simply b/c they're driven by different things.
yeah, and the "about" section doesn't really answer the question very well:
What is ether?
Ether is a necessary element -- a fuel -- for operating the distributed application software platform we are building: Ethereum. Without the requirement of payment of ether for every computational step and storage operation within the system, infinite loops or excessive storage demands could bog down Ethereum and effectively destroy it.
I regularly use Muni line 29. At least a couple of times a week, commute hour buses do this. Usually it works out okay for two reasons:
1. The next bus is right around the corner or I have my transit App to give an idea about delay if I cannot see the next bus yet. generally the delay is of teh order of 2 ~ 3 minutes.
2. The next bus is also has less people and the journey is thus more pleasant.
Things do screw up at times though. This weekend, a driver did not stop and indicated that there was a bus following him. The App showed the next bus was 20 minutes behind. I had to catch a different bus after that. I hope this does not happen on working days.