Mayayana
6/2/2012 2:50:00 PM
| On the sentence: "The people at Microsoft did that because that's what
| they thought they heard the Visual Basic 6 community demanding."
|
| Where did they get that idea from? As I recall, from the instant the
| first rumours of Visual Basic .Net started appearing, the classic VB
| community was up in arms about it, and the cacophony of opposition
| still hasn't died down, even today.
I think what he was meaning to say was that MS thought
most VBers wanted more power, so when they were designing
VB.Net they [allegedly] provided more power. (It's hard to
see that logic when MS was switching the model from
compiled software to Java-clone web service software. I'm
guessing that Mr. Platt subscribes to the Tom Shelton School
of Surreal Beliefs. :)
As I understood it, Mr. Platt was saying that 97% of VBers
are halfwits and 3% are halfwits who dream of achieving
fullscale humanity... and that MS overestimated the size
of the latter group, thus giving them an overly functional
toolset, beyond their level of comprehension, with VB.Net.
My impression has always been nearly the opposite: MS
added increasing functionality with each version. (Wasn't
AddressOf added in VB6?) The leading developers were
in accord. Matthew Curland was on the "VB Team", wasn't
he? His book is full of API trivia, optimization tips, and
inline assembly. He's got nothing about building a database-
frontend ActiveX control out of a frame and textboxes.
But by the time VB6 was ready for an update,
MS was thinking they had plenty of Desktop developers;
they wanted to push people into web services because they
thought that was the future; and they wanted to start pushing
3rd-party developers out of Windows itself because they were
eyeing the potential of being a middleman for music and video
sales, through a future Windows version that would be something
like interactive TV. So... They created .Net as a sandboxed web
services tool to compete with Java. Then .Net was handy as
a way to start pushing people off of Windows. ("Did we say that
..Net was a web services tool? We meant to say .Net is the best
thing going for Desktop software. Mangia! Mangia!")
And now, finally, MS may be close to achieving restricted,
interactive TV with Win RT/Metro, and even .Net is too
"low-level" to be allowed to live on as anything more than a
a clunky way to write web service trinkets on top of WinRT.