902 karma · joined November 19, 2012
topcolor: FF0000
Not only are these strategic moves, they are strategic moves by a large company aimed at competing with people like me who develop software on multiple platforms and contribute, unpaid, to an open software ecosystem.
Looking at US job search sites, Java has about 2 times as many results as C# in the US overall, and 3-6 times as many in SF and New York. Java even has almost twice as many results in Seattle.
From indeed.com:
Java - 81,818 [1]; C# - 35,623 [2];
[1] http://www.indeed.com/jobs?q=java&l=
[2] http://www.indeed.com/jobs?q=C%23&l=
comments:
- Java has more results than even ".NET", which encompasses more than just C#: 73,971 http://www.indeed.com/jobs?q=.NET&l=
- C# has about the same number of results as Python: 35,072 http://www.indeed.com/jobs?q=python&l=
From StackOverflow:
Java - 794 [1]; C# - 479 [2]
[1] http://careers.stackoverflow.com/jobs?searchTerm=java
[2] http://careers.stackoverflow.com/jobs?searchTerm=C%23
From indeed.co.uk (the only one that has a similar ratio as itjobswatch.co.uk):
Java - 25,478 [1]; C# - 28,037 [2]
[1] http://www.indeed.co.uk/jobs?q=java&l=
[2] http://www.indeed.co.uk/jobs?q=C%23&l=
From indeed.com, Bay Area:
Java - 5,997 [1]; C# - 1,013 [2]
[1] http://www.indeed.com/jobs?q=java&l=San+Francisco%2C+CA&radi...
[2] http://www.indeed.com/jobs?q=C%23&l=San+Francisco%2C+CA&radi...
From indeed.com, New York:
Java - 6,941 [1]; C# - 2,548 [2]
[1] http://www.indeed.com/jobs?q=java&l=New+York%2C+NY&radius=25
[2] hhttp://www.indeed.com/jobs?q=C%23&l=New+York%2C+NY&radius=25
From indeed.com, Seattle:
Java - 3,832 [1]; C# - 2,124 [2]
Defaulting to the position of criminalization regardless of the evidence, particularly in this context given the history and impact of existing marijuana policy, will likely perpetuate the creation of flawed policy.
The research about Marijuana's impact on driving is inconclusive, but there are indications that it might have no negative impact (for the most recent example: https://s3.amazonaws.com/s3.documentcloud.org/documents/1667...) and even that it might reduce risks of crashes.
As a result, it's unfortunate that it's apparently socially acceptable to assume without question that marijuana has a negative impact on driving. New research could still demonstrate that it does not, just as new research has been strongly suggesting that our other assumptions are likely flawed. If marijuana is found to not be dangerous for drivers, then it will very unfortunate that we've promoted yet another misconception about it due to unchecked assumptions.
https://www.google.com/search?q=site:theguardian.com+iphone
See the sections "capitals" and "company names" here http://www.theguardian.com/guardian-observer-style-guide-c
In particular:
"In general, we use the names that companies use themselves: c2c, Capgemini, easyJet, eBay, ebookers, iSoft Group, etc."
http://www.npr.org/blogs/codeswitch/2014/04/27/306829915/seg...
Compare these two Stack Overflow "getting started with" answers for Haskell http://stackoverflow.com/a/1016986 and F# http://stackoverflow.com/a/11974625 With the Haskell answers I don't know or care what platforms, operating systems, editors, or IDEs they are using. With the Microsoft answer it's like a dystopian scene filled with Branding, Branding, and more Branding.
Personally, I spend a lot of time experimenting with languages and ecosystems and the ".NET" platform is the only one where I feel the need to put on a plaid shirt and dockers with a Windows Phone on my belt and schedule a conference call with a committee at Microsoft to tell them to give it a rest already.
Gecko exists.
Furthermore, having many browsers using Webkit, Blink, and Gecko isn't "bad," and calling it a "monoculture" is a weasel word attempting to link it to the problem of IE's dominance in the 2000s. The problem with the 2000s IE monoculture wasn't just that it was a monoculture, it was that it was closed source, stagnant, and mostly single-platform. Webkit, Blink, and Gecko aren't.
There are a lot of benefits that come from using mainstream existing frameworks and libraries from the beginning. You learn conventions pretty quickly, and immediately learn to write idiomatic code for that language. When you use a major framework or library there are typically a lot of blog posts and stackoverflow answers, more so than just for a language itself. When you track down errors you'll end up learning about how the frameworks and libraries work, and thereby learning about how to implement things you wouldn't have considered independently.
As a result, what I'd recommend is coming up with two extremely simple ideas for tools that he'd find useful for himself and implement one each with Ember and React.
Personally, I've been following this approach for many years (I'm currently simultaneously working on three new projects in multiple new-to-me languages like this) and it works extremely well in my experience.
http://patorjk.com/blog/2012/01/26/pronouncing-sql-s-q-l-or-...
It's like if someone took a bunch of iron beams, claimed that they were actually 100% natural wood, and managed to get a bunch of people to buy them.