I think you are referring to Scott McKinney. Scott is/was a big name in the VB community. He has/had issues with MS regarding the direction of VB and how VB has progressed through time. As a big hitter in the VB community, he went public with his exit. I have said this for quite some time that there are a bunch of folks in the VB community that are very disenchanted with VB. Sound familar?? Folks like this can be found in every community.

With regard to the editorial you cite, I classify that as part of the "whine-fest".....

>Does this explain the editorial I saw in VBPJ several months back from the author of "Hardcore Visual Basic".
>
>In case you forgot this one, he had a big editorial complaining how he had set up this elaborate framework to work with VB 5 in his book. He had been asked to update his book for VB 6. But his framework now bombed in several key areas. He was told by MS that certain fnctionality had been changed, this of course included fixing things that were broke before, but he had programmed for the broken code.
>
>Are "Hardcore..." type programs best left for VC ++?
>
>PF
>
>
>>Hi Craig...
>>
>>In a word, all this stuff is a bunch of BS.... I can't tell you how sick and tired I am of hearing from a faction of the VB community that insists on making the product more like C++. Many of these folks detested the data-centric capabilities VB received in 6.0. Rather, they wanted more low-level control, pointers and such. The fact is, there are alot of things VB can do. In most cases however, many of these folks should look to C++ for this type of work. Personally, I think Ash is unfairly bashing the product. He is basically labeling it as unfit for large-scale enterprise developement. That simply is not true.