Re: Moving On


"mayayana" <mayaXXyana1a@xxxxxxxxxxxxxxxx> wrote in message
news:EaRRg.12389$v%4.2370@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
It seems to me that your making the common,
and rather odd, assumption that there's a
"VB road" and that it goes along the route
you're travelling.

If MS had invented Java
they might have called it "MyNewC++" and
asked the C++ programmers to move. (Which
they apparently *are* doing now with C++/CLI.)
But so what? What do Microsoft's marketing
plans have to do with anything?

I just don't see how so many people think it's
reasonable to equate native-compiled EXEs with
VM-hosted JIT-compiled software.
Note there is still virtually no Java Desktop software
to this day. I don't even have the Java VM installed
because, like the .Net runtimes, I have no use for it.
That's not to say that Java is irrelevant; just that it's
different.

Personally, I don't want to go where MS is going,
but if I were going to go to the trouble of getting
into .Net then I think I'd go to C#. No one seems to
take VB.Net seriously. In my travels for source code
I'm seeing an increasing amount available for C#
but not for VB.Net.

So, good luck. I just hope you won't become one
of those lurking, overcompensating dotNetHeads
who continue to hang around here trying to save souls.

On second thought....maybe you should. I suspect
that once MS gives up on converting the remaining
VBers then either the lights will go out on
microsoft.public.vb.general.discussion, or a fair-size
army of dotNetHeads will be ordered to start
chatting here. :)



I believe it is rather obvious that M$ has no intention for dotNet to be a
tool for developing "Shrink-Wrap" or "Desktop" applications. That market is
stalling out any way - it has become a commodity market with very low
margins. The future is all dedicated embedded toys and web-based services.
For neither of these was VB ever an ideal tool.

That doesn't mean there isn't a need for Desktop apps, nor that some will
still continue to make money, it just means they will either stick with VB
or seek another tool. M$ could care less.

dotNet is for high-bandwidth intra-nets and for backend internet
applications. It is tailor made for intra-office business suites. I have
found that once a team adopts dotNet for in-house integrated apps - classic
VB looks downright awkward. But as you pointed out dotNet is not a solution
for every situation.

As for your last comment, I doubt M$ really worries about this newsgroup one
way or another.

-ralph


.

Relevant Pages

  • is dotnet right for my requirements?
    ... I'm new to dotnet. ... Ability to run on a desktop with no internet (stand-alone, ... go with Java and use their webstart technology to accomodate this. ... there's an easy way to go from a vb.net app to an asp.net app? ...
    (microsoft.public.dotnet.general)
  • Re: OpenQM vs. Everything Else
    ... As you rightly say, Dawn, with dotnet - and with technologies such as Java, ... about Java can be written on the back of a small stamp with room to spare... ... If what a VAR or developer is offering to a prospective client isn't ... Taking an anti-MS ...
    (comp.databases.pick)
  • Re: Envryption interop between .NET and java
    ... in java init the IV goes like this: ... bytes in dotnet are unsigned while in java are signed.. ... that should encrypt the same string and produce the same encrypted ...
    (comp.lang.java.security)
  • Re: confused abt what to choose!
    ... for DotNet only thats y i m askin y shud i preffer DotNet language ... C# is a generally nicer language than Java, ... Java has wider 3rd party support in terms of open source libraries ... Studio - there tends to be better support for actual coding, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Will VC++ face out ?
    ... Can C# support standard or Win32 C/C++ class lib dll and COM? ... Can dotnet and Java do device IO control with drivers? ...
    (microsoft.public.dotnet.languages.vc)