Oh, Silverlight is a 'plugin', a plugin need to be compatible with more hosts, so a 64bit version is necessary, bloated or not.
On the other hand, Visual Studio is an ecosystem, it need to be compatible with more 'plugins', even itself is assembled by lots of plugins, so having a 64bit version of shell means much more work for internal teams and external partners, different story.
Huh, Rico was working on some 'internel incubation project' from summer 2010 to winter 2011.Rico Mariani became my boss last summerwas working on an internal team that I could not write much about for the last couple of years
I know its completely off-topic but ......
3 hours ago, exoteric wrote
That said, I seem to remember a comment when Windows 8 was first demoed publicly by Sinofsky and, Julie Larsen, where there was a remark that made it seem like HTML 5 development had suddenly been raised to a preferred method of developing apps for Windows 8. Of course that's nonsense and anyone with common sense should be able to deduce what was meant. It does show how easily confused people get about future directions.
I'm sure Felix can track down the comment - although it's just for historical curioisity at this point.
Hmm... no, believe it or not, it didnt sounds like the HTML5 is the 'preferred' way, instead, it sounded like HTML5 is the 'only' way for the new UI ! everything else is still supported but just for the old UI !
People knew it can't be true, but its still 'poor developer communications and PR'
To be fair, Charles clarified this the next day on Channel9 https://channel9.msdn.com/posts/A-quick-look-at-Windows-8#c634425734130000000
but this was almost the ONLY outspoken MS employee for three months, in a comment of a post ! Peter Brown may be another one, everyone else was saying "None of us at Microsoft can say anything until //build/ in September." Ouch.
Even MaryJo Foley wanted to stop the FUD
But people still had this impression in August.
All in all, this ridiculous thinking might be a result of 'speculation', but stupid PR from Microsoft definetively set it off and helped a lot to spread it.
Scott Hanselman was obviously joking in that podcast I mentioned, but the joke itself reflects the situation of reality, isn't it ?
OK. That's all for today's history lessons, lets move along.
Nitpicking, Bartok does have a option "nullgc" which means no collector
The only problem is your memory wont be reclaimed, but if you dont allocate much its OK I think.
Oh, if you really want to hear from Anders himself then here it is, about 30 ~ 35min
for WinRT and .NET discussions, maybe this episode of Hanselminutes is a good oneScott's confused about what 'WinRT' is. Is it a new .NET? A new runtime? Is .NET dead? He's totally confused so he talks to Immo Landwerth who sets him straight with complete context from Win32 to COM to .NET and beyond.
articles like these appears and went to Slashdot.
IMHO its the result of the secrecy policy of Sinofsky about Windows 8. Giving a little bit of message once a while and keep mouth shut when people are in doubt and having questions, its very frustrating and kills trusts and confidence.
So, maybe a little bit of error messages can help us understand what CrossGen can do for us ?
most of them are the same as in clrjit.dll, but maybe crossgen can do more aggresive cross-module inlining ? http://www.freepatentsonline.com/y2011/0225564.html