Tom Shelton
9/13/2011 8:18:00 PM
Mayayana formulated on Tuesday :
>> I just
>> can't really imagine using VB6 for any new serious development...
>>
>
> ...Or .Net.
..NET is still a major part of windows 8 - which makes sense because of
it's jit behavior. Look at the slide.
> It's all still gossip at this point, but
> my impression was that MS is aiming for HTML
> and javascript in a version of IE that's tied into
> the Windows API.
Partially right. The trident rendering engine from ie 10 will be used
to render the new desktop. But, you don't have to develop that ui
using html5 or javascript. Those are just another option.
> Compiled software would be
> a grudging optional extra to run in the "Desktop
> tile".
>
Nope. Look at the slide. Metro UI apps. Taht's the new desktop.
Now, older winform, silverlight, wpf, native apps, and vb6 apps will be
there - but, all of those code bases - except one - have the option of
rewriting their UI's and becoming first class citizens again.
> On the other hand, that whole idea seems so
> absurd and unwise that I have to believe it's a
> temporary case of cloud/tablet-fever.
As much as I'm not a huge fan of the paradigm, I don't think it's going
away anytime soon.
> After all,
> MS was talking about converting the API to an
> easy, OO managed sandbox almost 10 years ago.
> ...It never happened.
Apparently, it has now. It's called WinRT.
> What was it they called
> that? I think it was something like ".Net". That idea
> was as wacky as this new web-app trip. Lucky for
> us, they stuck with native code and COM. :)
It's not about web apps. It's about touch friendly interfaces, etc.
But, I already know you are ludite of sorts - so, there is not need to
argue about it.
--
Tom Shelton