Is VB Caca??

  • Thread starter Thread starter Don
  • Start date Start date
Send in the trolls. :(

PFC said:
Goran


objects are worthless; they make code run slower

your whole premise is screwed

vb6 works _FINE_ without all this object _CRAP_

sorry; don't use VB.net it is a compelte failure

you shoudl just use C# because that's the trendy thing to do; and
people will snicker and call you a wuss if you use VB



-PFC Sadr
 
Tom Leylan wrote:
Frankly I don't see the
syntactic advantage to Sub at all, they can as easily be declared as
functions that return Nothing.

But then you would have to look up the documentation for every function
that you use, to see if the return value is supposed to be used or not.
Now you know that if it has a return value, it always means something.
 
You missed the hours spent debugging this garbage. Looks like something
Aaron Kempf or "Master Programmer" would write.

Mike Ober.
 
Göran,

Göran Andersson said:
Well, parantheses has been used to access arrays in BASIC for more than
fourty years, so I don't really see that changing. The support for
subroutine calls with parameters is a much newer addition to BASIC, but
parentheses are used for this in so many languages, that I don't really
see a change there either.

I gess you are stuck with the parantheses. ;p

I do not have a problem with the current solution, but I only mentioned
array syntax because I wanted to show that I am not the greatest fan of all
solutions that have been chosen for BASIC/VB.
 
PFC Sadr said:
VERBOSITY
VERBOSITY
VERBOSITY
VERBOSITY
VERBOSITY
VERBOSITY
VERBOSITY

Well, with the VB IDE generating most constructs for you one often needs
less keyboard hits than in the less verbose C#, for example, to archieve a
certain goal. Verbosity isn't a bad thing in general if it helps to
understand the code and makes reading easier (which is archieved by
similarity to the natural English language in VB). Take '&&' vs. 'AndAlso'
for example. How would you tell a coworker on the phone what your code
looks like? So there are many things to consider when talking about
advantages and disadvantages of verbosity and similarity to natural
languages.
 
I call for an all out war against Microsoft

I agree. I suggest you start by boycotting their newsgroups.
 
Göran,

Göran Andersson said:

It's much easier to postulate things than to back them up with arguments (no
offense against you intended). The author of the Web site not only is not
at the current state of development for VB (but interestingly for C#), he
doesn't even see a link between VB and C#.
 
I think that it pretty well describes how his mind works. Whatever the
requirements, whatever the situation, the answer is always the same.

Opinion revealed
Load and clear to hear
A parrots voice
 
Herfried said:
Well, with the VB IDE generating most constructs for you one often needs
less keyboard hits than in the less verbose C#, for example, to archieve
a certain goal. Verbosity isn't a bad thing in general if it helps to
understand the code and makes reading easier (which is archieved by
similarity to the natural English language in VB). Take '&&' vs.
'AndAlso' for example. How would you tell a coworker on the phone what
your code looks like? So there are many things to consider when talking
about advantages and disadvantages of verbosity and similarity to
natural languages.

Don't feed the trolls. :o

Anyway, I share your view on verbosity. :)

Also, considering how small a part of the programming the actual typing
really is, I don't really understand the fear of verbosity. If typing a
few letters less really would have any impact on your efficiency, then
your project can't be very challenging...
 
Göran Andersson said:
Respect for that. :)


Yes, I can see how you get that feeling from some of my posts. I like the
debate (which I admit is a bit risky), and I can argue strongly when I
feel that there is a deeper truth that would benefit from being revieled.

I try to keep opinions in threads that are about opinions, though, and I
think that you have to admit that in other threads you couldn't even tell
that I have written a single line of C# in my life.


I think that you can express an opinion about a language without
absolutely having to comparing it to any other language. For example,
there are things about VBScript that I think sucks big time, but that
doesn't mean that JScript has to be any better at it.

Also, if I avoid comparing VB.NET to a specific language, I can
implicitly compare it to languages like Pascal, Turbo Pascal, Delphi, C,
C++, Cobol, Fortran, BASIC, GFA Basic, ST Basic, GW Basic, Comal,
VBScript, JScript, Javascript, VBA, VB 6 and C#. I think that it gives
quite a wider perspective. :)


Wise words. I will also continue to try to keep it on a level where it
might be enjoyable to read and participate. :)

Fair enough. Have fun!
Robin S.
 
MP left the group quite a while ago. It's one of AaronKempf's aliases.

Robin S.
----------------------
 
Scott;

that's funny

the punchline of course; is that this is MY NEWSGROUP and I'll say
what I want; when I want and where I want

when Microsoft makes a newsgroup for VB that doens't include the word
DOTNET is when you can have your turn to talk

WHY ARE WE IN A NEWSGROUP TALKING ABOUT VB AND ITS NO LONGER CALLED
DOTNET?

WHAT IS WRONG WITH MICROSOFT.PUBLIC.VB?
 
You'll have to argue with Herfried and/or Cor who suggest that C# is like
VB. If that is the case then surely returning Void is an option right?

Are there Sub declarations in C#? If not considering it's similarity to VB
why not?
 
Michael

for the record; I'm a damn fine programmer

you see:

a) experience programming BASIC since 1982
b) the balls to 'question authority'
c) refusal to be a fair-weather freind and jump on the programming-
language-of-the-month bandwagon

I'm not a bad programmer kid

I'm sorry that you're getting paid to spread FUD.
you can lick my nuts; kid

-PFC Sadr
 
you're right

the answer is the same

the answer is VB6 not this DOTNOT crap


dotnet can't even be utilized in 1/4 of the situations where I've been
usign visual basic every day for 10 years
when .NET has 1/2 of the functionality of Vb6 is when I give it
serious consideration

when I can cut and paste from VB into Excel is when I STFU
when I can cut and paste from VB into SQL Server jobs is when I STFU

as it is--- DOTNOT is a 1/4 solution

yeah.. it can build executibles.

BIG FRIGGIN DEAL.

can I run VB.net ON THE CLIENT BROWSER?

WHY NOT?
 
Huh? Seriously though why would anybody call a function if they didn't know
what it did and/or returned? Nobody just calls things for no reason. In
any case doesn't anybody calling a function that does return a value sit and
wonder what datatype is returned?

Believe me it would make no difference.
 
Tom Leylan said:
You'll have to argue with Herfried and/or Cor who suggest that C# is like
VB. If that is the case then surely returning Void is an option right?

"C# is like VB" is too generalized.

C# is like VB as both can be used to create applications which run on the
CLR and make use of the .NET Framework.

The MSIL provides some features in the style they have been already
available in VB6, such as properties, for example. Consequently they are
supported by C# in a similar way.

It's always hard to tell which languages influenced another one if a certain
feature is present in more than one existing language. Take short-circuit
logical operators ('AndAlso', 'OrElse') as an example. Does this mean VB
has been influenced by C ('&&', '||')? The answer is, like in the case of
properties, yes and no.

Thus it's important to make a distinction between similarities and the
influence of one language on another.
Are there Sub declarations in C#? If not considering it's similarity to
VB why not?

The term "similar" is not the same as "equal".
 
Herfried said:
Göran,



It's much easier to postulate things than to back them up with arguments
(no offense against you intended). The author of the Web site not only
is not at the current state of development for VB (but interestingly for
C#), he doesn't even see a link between VB and C#.

I don't really see much of a link between VB and C# either. They are
quite dissimmilar languages.

VB.NET and C# share the .NET framework, but that doesn't have anything
to do with the actual languages. Most any language can be made to use
the framework, but that doesn't mean that it suddenly has influenced the
development of C#.


Here are some hard facts to back up it up. :)


"An evolution of Microsoft C and Microsoft C++, C# is simple, modern,
type safe, and object oriented."
http://msdn2.microsoft.com/en-us/vcsharp/aa336766.aspx

"Anders Hejlsberg, a distinguished engineer at Microsoft, led the team
that designed the C# programming language. Hejlsberg first vaulted onto
the software world stage in the early eighties by creating a Pascal
compiler for MS-DOS and CP/M. A very young company called Borland soon
hired Hejlsberg and bought his compiler, which was thereafter marketed
as Turbo Pascal. At Borland, Hejlsberg continued to develop Turbo Pascal
and eventually led the team that designed Turbo Pascal's replacement:
Delphi. In 1996, after 13 years with Borland, Hejlsberg joined
Microsoft, where he initially worked as an architect of Visual J++ and
the Windows Foundation Classes (WFC)."
http://www.artima.com/intv/generics.html

"In the design of C#, we looked at a lot of languages. We looked at C++,
we looked at Java, at Modula 2, C, and we looked at Smalltalk."
http://www.windowsdevcenter.com/pub/a/oreilly/windows/news/hejlsberg_0800.html
 
Back
Top