Is microsoft awaring VB.Net too hard to maintain?

  • Thread starter Thread starter mentochan
  • Start date Start date
M

mentochan

It was heard that VB is not fitful for OO programming, and MS is
falling into a hardtime to maintain such product. I myself don't think
it's true.
Is there any articles talk about this?
 
Mentochan,

I assume that VB Net is more OOP than C++ and C#. As I read these newsgroups
than VB Net programmers become at a certain moment more converming the
rules, while for C++ and C# programmers probably old C rules are for them as
well OOP.

However it is as well usable while ignoring that.
(There are 6 million programmers probably converting you know, a little bit
more than with other languages).

Cor
 
It was heard that VB is not fitful for OO programming, and MS is
falling into a hardtime to maintain such product. I myself don't think
it's true.
Is there any articles talk about this?

No, because it's not true...
 
I've just seen personal opinions such as :

"There is no need for another language and developing VB.NET took resources
away from developing the framework. The framework library shows signs of
poor design and cut corners and I think that if Microsoft hadn't diverted
its resources towards VB.NET then the framework library would have been much
better."

(quoted from http://www.grimes.demon.co.uk/dotnet/vbpetition.htm)

I wouldn't worry much about this...
 
I suspect that with 30 billion in cash even after the 3 dlr per share special
dividend and earnings increasing 10 to 15% each year that M'soft has the
resources to develop both VB.Net and FrameWork.
 
Patrice said:
I've just seen personal opinions such as :

"There is no need for another language and developing VB.NET took
resources away from developing the framework. The framework library shows
signs of poor design and cut corners and I think that if Microsoft hadn't
diverted its resources towards VB.NET then the framework library would
have been much better."

(quoted from http://www.grimes.demon.co.uk/dotnet/vbpetition.htm)

Microsoft doesn't sell the .NET Framework, it sells IDEs. I doubt that many
former VB6 users would have migrated to a Microsoft IDE at all if there was
not VB.NET.
 
Why then is most of the sample code I find on the Internet written in
C#? I've found that some things done in C# can't be done in VB. I will
continue using VB nonetheless.
 
Kevin,
Why then is most of the sample code I find on the Internet written in
C#? I've found that some things done in C# can't be done in VB. I will
continue using VB nonetheless.
I think that you have to wait until those 6 million are over.

There is very few to what you can do more in C# than in VB.Net (unsafe
code).

For the rest I am curious what you have found what can be done in C# 2005
more than in VB.Net.

The same is for C# which can almost completely use the Visual Basic
namespace.

However I real C# programmer would not do that, I think something the same
as a real Englishman would not drink Dutch or Belgium beer some decenia ago.

:-)

Cor
 
I'm just now making the switch from VB6 to VB2005, so I haven't had a
lot of experience with it. I've found one thing so far when trying to
create a custom class from a Combobox. I found sample code on both and
tried making the methods and properties I wanted from between the two.
In C# you can create a ReadOnly property for a Combobox while VB won't
let you use the Keyword.

I never had Dutch beer. Is it better than American beer?
 
VB.NET can do a read only property....

Public ReadOnly Property MyPropName as Type
Get
return MyValue
End Get
End Property
 
well the person who wrote that petition needs to get their mind out of the
past and learn true OOP... VB6 was HORRIBLE compared to the OOP C# and
VB.NET brings... and because of them that stupid My namespace was included
in VB2005 (ok some of it is nice, but default instances? please.... get rid
of that junk)
 
I would say that VB.NET and C# is about equal when it comes to OOP.

My opinion is that C# feels more object oriented, but that is only
because the syntax in VB.NET is somewhat awkward. C# was designed for
OOP from the ground up, but with VB.NET it was added into a procedural
language.

Old C rules does not apply to OOP, as C is not object oriented. :)
 
Kevin,

On our website is a lot of code and not one piece C# (although we are able
to that)

http://www.vb-tips.com/default.aspx

I don't know how old you are and know that the USA has strict laws. If you
are old enoug, did you real never drink Heineken. Than you are probably one
of the last mans on the world who did not.

:-)

Cor
 
Kevin,

Completely of thread but whatever, at the moment I don't drink beer anymore
but from my history about beer.

I like American beer as Budweiser and Miller. However if you once have the
chance than go to Czech.

There you can drink Urquel and real Budweiser from draft, than you are
talking about no other beer anymore. (The bottles with those don't reach in
my opinon not in any way the taste from draft in Czech what has by other
beers not so much difference). If you don't believe me, ask Herfried, he
lives near Czech.

Cor
 
Also completly, 1000% OT,
but you haven't had a real beer before you have tasted the fine belgian
beers :-)
I've never met a finer beer then a nice belgian beer called "Duvel" or
"Blond Leffe", if you ever get the change taste them.
This weekend I was in Groningen were they served me Grolsch and thought
maybe this will convince me of the good dutch beers but it tasted even worse
than I imagined ;-)
As you may have noticed, we Belgians love our beers but that's only because
they're the best in our opinion and everyone else's who's ever had one :-)
So if you ever get the change, taste one of the 500+ sorts available

http://en.wikipedia.org/wiki/Belgian_beer
 
I think that microsoft made a big mistake by developing the C#. VB.NET is a
new language comparing it with VB6. Microsoft could make more changes in
order to make it a real Object Oriented Language (I beleve that it is, but
some of you does not belebve it). The result of all this is that there are
two big group of programmers, some of them use VB.NET and some others use
C#. Now if someone needs a pice of code in VB.NET he might have to translate
an existing program from C# and vice versa. For them who beleve that VB.NET
is not an Object Oriented Language, I thing that they have developed all
their projects in C#, and they do not have any idea what VB.NET is.

Aristotelis
 
Smokey Grindle said:
well the person who wrote that petition needs to get their mind out of the
past and learn true OOP... VB6 was HORRIBLE compared to the OOP C# and
VB.NET brings... and because of them that stupid My namespace was included
in VB2005 (ok some of it is nice, but default instances? please.... get
rid of that junk)

Well, it's pretty obvious that you didn't undestand the goals of the
petition.
 
Göran Andersson said:
My opinion is that C# feels more object oriented, but that is only because
the syntax in VB.NET is somewhat awkward.

Interface implementation based on identifier equality feels more
object-oriented than declarative interface implementation?
C# was designed for OOP from the ground up, but with VB.NET
it was added into a procedural language.

Well, as a result VB.NET is more flexible than C# :-).
 
Peter,

Was you ever in Tjechy. If you were not there you cannot talk about beer.

I once drunk I thought as well in Groningen in a bar a lot of that beer with
that woman's name.
The next day I had an headage I never had before from beer. It could have
been me but in that time it was containing a lot of sulphite. Therefore I
like Heineken it has 0% sulphite.

I have too drunk once some Belgian dark beers. I could not drink them, is
was as English Bitter and decoded never to drink any Belgian beer any more.
It was not Suske. That decision has changed.

Nevertheless, there are very good Belgians beers, but you surely have once
to go to Tjechy and drink from draft (not bottle) to be able to judge.

:-)

Cor
 
Back
Top