4 ms·
A CLR doesn't solve much I think, if you look at .Net there's a single de-facto language (C#) and VB.NET died out just because people will gravitate toward the
by eterm 12y ago
A CLR doesn't solve much I think, if you look at .Net there's a single de-facto language (C#) and VB.NET died out just because people will gravitate toward the language which has all the help, stackoverflow answers, etc.
Sure, it makes using other languages possible, but typically that'll just be seen as weird.
- raziel2p 12y agoYou can't really compare the two situations (.NET and a hypothetical browser bytecode/VM). The reason C# ended up the main .NET language is that it's a brilliantly designed language - far more than you can say about Javascript.
- ufo 12y agoI don't think its just that. Its impossible to design a "trully general" intermediate programming language so what ended up happening is that the CLR was a perfect fit for C# and a not-so-perfect fit for everything else. At least thats what I've been told by my programming languages professor.
- emodendroket 12y agoWell, there are others, but maybe the JVM is a better example, where Scala seems popular enough.
- tonyedgecombe 12y agoI think VB.NET was just tainted by Visual Basic. Back when it was released there was a lot of resistance from the VB crowd where as all the C++/MFC programmers could see a huge and immediate benefit in C#.