dilettante
MIS
I'm not seeing any chatter about this here yet. Of course the whole thing is only a few weeks old at this point.
So far I'm seeing a few posts on VBx:
... and of course lots on Silverlight itself, which looks/smells like a Flash competitor. This used to be called WPF/E.
So it appears that "VB" (or at least the .Net incarnation) is being positioned as a VBScript/VBA replacement for both Windows and Mac. Probably outside Silverlight it'll first emerge in a new Office release. No idea what this means for PowerShell but perhaps we'll see some convergence.
I also can't be sure whether this means VB.Net will "lose its legs" as it follows this evolutionary path or not. Maybe VB.Net will vacate its niche alongside C# for "traditional" CLR (non-DLR) development? I pity the poor fool who decided to invest heavily in VB.Net if that is true.
I have my doubts though. The Silverlight 1.1 JavaScript-to-IL compiler was built in VB.Net. Maybe VB.Net is simply splitting into two parallel paths like the old VB/VBA dichotomy? A pretty well-circulated "poster" graphic mapping the Silverlight universe seems to list both VB.NET and VBx.Net (listed as Visual Basic and VBx respectively).
Platform coverage seems to include IE 6 & 7, Firefox 1.5 & 2.0, and Opera... on Windows 2000 through Vista and Mac Leopard & Tiger. A sort of stripped CLR weighing in at about 4MB seems to be at the core. I assume from the chatter that it contains at least some of the "dynamic language" support so maybe it's more of a stripped DLR.
Isn't technology churn wonderful? Anyone else having trouble keeping up?
So far I'm seeing a few posts on VBx:
... and of course lots on Silverlight itself, which looks/smells like a Flash competitor. This used to be called WPF/E.
So it appears that "VB" (or at least the .Net incarnation) is being positioned as a VBScript/VBA replacement for both Windows and Mac. Probably outside Silverlight it'll first emerge in a new Office release. No idea what this means for PowerShell but perhaps we'll see some convergence.
I also can't be sure whether this means VB.Net will "lose its legs" as it follows this evolutionary path or not. Maybe VB.Net will vacate its niche alongside C# for "traditional" CLR (non-DLR) development? I pity the poor fool who decided to invest heavily in VB.Net if that is true.
I have my doubts though. The Silverlight 1.1 JavaScript-to-IL compiler was built in VB.Net. Maybe VB.Net is simply splitting into two parallel paths like the old VB/VBA dichotomy? A pretty well-circulated "poster" graphic mapping the Silverlight universe seems to list both VB.NET and VBx.Net (listed as Visual Basic and VBx respectively).
Platform coverage seems to include IE 6 & 7, Firefox 1.5 & 2.0, and Opera... on Windows 2000 through Vista and Mac Leopard & Tiger. A sort of stripped CLR weighing in at about 4MB seems to be at the core. I assume from the chatter that it contains at least some of the "dynamic language" support so maybe it's more of a stripped DLR.
Isn't technology churn wonderful? Anyone else having trouble keeping up?