Re: Microsoft and trust

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

| I think it's a fairly significant point. People say there is an issue of
| trust but show a big contradication with vb6. This indicates it not really
| an issue of trust but more along the lines that they just don't like dot
| net.

Not entirely true. I participated in the "VB7" beta (must have been later
on as they were calling it .net by then) and didn't much care for any of
what I saw. And that is not even counting the fact that I realized very
quickly that anything I tried to port from VB6 would require a significant
rewrite. That aside, it was slow, cumbersome and bloody redundant. Maybe
it also had to do with the fact that I wrote desktop apps. Shareware. To
which any flavour of .net is serious overkill. Tho whole concept of yet
another layer to work in seemed lazy and constraining. Not to mention that
anyone who wanted to crack my licensing schemes could very easily decompile
the app. Sorry, but in this case, JIT sucks. I realized at that early
stage as well that clearly, MSFT broke something that did not need fixing.

I tried 2005 when it was available and was equally unimpressed.

Tried 2008 as well and just don't see any reason to convert. As it's been
said many times, if I'm going to learn a new language, which is what vb.net
requires, I am going to move to something not MSFT, and not .net. It was a
bad idea from the get go. Sorry, but that is my opinion. If you don't like
it or agree, that's your right....but trolling this newsgroup isn't. If I
go to the vb.et newsgroup and post a ".net sucks" thread there, will you
move all this crap there as well and leave us folks who prefer vb classic
alone? Seriously...there is no need for all this bickering. It's making
this community not a fun place to participate in.

| I just give people a
| hard time because of what I consider to be fairly outrageous statements.

Well, then do it someplace where someone cares. No one asked you to come to
a newsgroup devoted to class VB and spout off .net propaganda. It's getting
bloody tiresome and painfully clear that there will never be a meeting of
the mind here no matter what each side says. It seems to me it would be
very easy for you .net folks to make the same statements in the .net groups
but yet for some reason I don't understand prefer to do it here where it's
not wanted. Is it just for the reaction? If so, that's pretty weak.
People come to *this* group for reasons pertaining to classic VB and this is
where the discussions should stay. Inviting yourselves here just to be
confrontational and disagreeable is silly and pointless and again...no one
cares. Folks who mispost here looking for answers to .net issues are
redirected to the appropriate newsgroup...it's not an invitation for .net
cheerleading.


.

Relevant Pages

  • Re: Microsoft and trust
    ... | trust but show a big contradication with vb6. ... quickly that anything I tried to port from VB6 would require a significant ... move all this crap there as well and leave us folks who prefer vb classic ... Why do we not give such warnings? ...
    (microsoft.public.vb.general.discussion)
  • Re: Problems with MciSendString
    ... in a .net group we'd get most people agreeing with me. ... most folks who use .net have next-to-no knowledge whatsoever ... to do xyz in vb6, how do I do it in .net" ... .NET: It's About Trust! ...
    (microsoft.public.vb.general.discussion)
  • Re: centering and sizing a word application active window
    ... VBA, I'd try asking in a newsgroup for classic VB (VB6). ... The folks there generally have a much better grasp of this ...
    (microsoft.public.office.developer.automation)
  • Re: Help: Visual Basic Setup Problems
    ... You will see how with very few code compared to by instance VB6 make things, you did not believe you could make without C++. ... newsgroup and the last and final version of Visual Basic is VB6. ... product, the one you are using, is a deliberate lie. ... such a deliberately dishonest act, but consumer law in most countries is ...
    (microsoft.public.dotnet.languages.vb)
  • Re: VB6 Error Handling
    ... That is what .NET had reduced folks to. ... Unfortunately I do VB6 for most of my time. ... the dotnet drawing group which is probably the area of dot net I know best. ... seem to ignore is that not everyone shares that opinion. ...
    (microsoft.public.vb.general.discussion)