A huge amount of code can / is be shared between the server and client, I wrote a database designed to work in browsers, a pull request away and it works in node.js using a different storage engine, 90% of the code is shared[1], the only people that arent convinced that sharing code between the server / client isnt useful just arent paying attention.
I do think having the templating portion of the web stack being in a client side language is important, as there's typically lots of overlap and interoperability that can happen at that layer between the client and server. As for the rest, I don't buy into the whole having a single language is better for understanding and hiring. Picking the right language that has the right metaphors for the problem will make things easier than having the same language everywhere.
It comes off as pretty funny that way, and helps make the point.
"He could shoot himself in the foot with a knife."
(Although JavaScript in particular is not an excellent language for anything.)
how many of these are over a year old? how well maintained are they? how battle proven? how well is v8 going to be maintained 10, 15 years from now? can we buy an extended support contract for v8 from Google?
these are also questions people in enterprise want to know. how well does it interact with our existing CLR/JVM stack that we've used for the last 10 years?
I have never been convinced by the "writing server side and client side code in the same language is good" argument, different jobs require different tools. Someone once said of this:
'you know how to use a knife, so you bring a knife to a modern war fought with guns, tanks, and missiles while shouting "at least I can use the same tools when I eat and when I fight! I save so much time!" before somehow managing to shoot yourself in the foot anyway.'