Microsoft, by seemingly ignoring the huge benefits of JIT-compiling VMs on
the browser and instead pushing Silverlight (which is pretty awesome though),
is showing it STILL hasn't gotten the Web. (The fact that I can't seem to
post on these newsgroups using Firefox (!!!) is yet another glaring example)
What is so ironic is that it has a golden chance to leapfrog Chrome without
even reinventing anything new, just stitching together pieces which it
One question I would have is if such a browser should / would support CLR or
CoreCLR (the refactored, smaller CLR Silverlight supports), or (heaven
forbid?) something in between.
CoreCLR is tiny, it along with all the other Silverlight assemblies fits in
only 4MB and still manages to provide most of the functionality of the .NET
Framework API that
People would be happily tolerate up to perhaps a 20MB (and up to 50MB quite
grudgingly) download for an out-of-the-box Silverlight-supporting,
[Core]CLR-based browser so it might mean that you could pack more of the .NET
Framework in there.