Re: VB.Net Rules!
- From: "PFC Sadr" <pfc_sadr@xxxxxxxxxxx>
- Date: 19 Feb 2007 14:35:59 -0800
re:
As VB.NET is BASIC with added features like type safety and object
orientation, it gets verbose. Most features are added by adding
keywords
to existing commands.
let's talk about events on forms.
I don't think that going 'twice as verbose' was necessary; helpful or
acceptable.
I won't use Windows Forms apps anymore and I sure as hell won't use VB
for ASP.net anymore; MS betrayed us all by removing vbScript DHTML
from ASP.net
why did they do this? VB won the war and MS threw the fight-- they
threw the world series; by surrendering to Sun Microsystems...
VB WON THE WAR.
AND MS SURRENDERED ANYWAYS.
it is right up there in 'the greatest betrayals of all time'
On Feb 18, 6:42 am, Göran Andersson <g...@xxxxxxxxx> wrote:
pfc_s...@xxxxxxxxxxx wrote:
so.. c# is the solution to VB.net code verbosity?
Yes, the only solution to make VB.NET less verbose is to make it not
BASIC. ;)
As VB.NET is BASIC with added features like type safety and object
orientation, it gets verbose. Most features are added by adding keywords
to existing commands.
Take for example the Dim command. In the original form it was only used
to create arrays by specify their dimensions (hence the name):
DIM A(4)
Regular variables would not be declared at all, just created when used.
To allow for explicit declaring of varibles, the DIM command was altered
to also allow for declaring regular variables:
Dim B$
To add type safety, the As keyword was added to the command:
Dim B as String
Similar ways of adding keywords can be seen througout the language.
I thought that VB6 was.
VB6 was a bit less verbose than VB.NET because it contained less
features. For example VB.NET is fully object oriented, which of course
adds a whole bunch of new keywords.
I am not going to embrace dotnet until the next version; I've been
saying that for several releases now.
I just can't deal with a bloated IDE that crashes on me.
I refuse to do it.
Sadly you have no choise in the long run. VB6 is replaced by VB.NET, so
MS will drop the support for it entirely in a few years.
On Feb 16, 5:01 am, "Earl" <briks...@xxxxxxxxxxxxxxxxx> wrote:
I miss VB6 and "classic" ADO ... but I aint going back. There are too many
new tools that make my life easier. I'm sure that was part of the Microsoft
master plan. However, if you like VB.Net, you would probably like C# even
more. The hands, wrists, and bursitis appreciate not having to type as much.
"Master Programmer" <master_program...@xxxxxxxxxx> wrote in message
news:uWxC0sUUHHA.868@xxxxxxxxxxxxxxxxxxxxxxx
I love VB.Net! The next version is going to be even better. I'm sorry if I
offended anyone with my rants. Please forgive me. OK?
--
Göran Andersson
_____http://www.guffa.com
.
- Follow-Ups:
- Re: VB.Net Rules!
- From: mg
- Re: VB.Net Rules!
- References:
- VB.Net Rules!
- From: Master Programmer
- Re: VB.Net Rules!
- From: Earl
- Re: VB.Net Rules!
- From: pfc_sadr
- Re: VB.Net Rules!
- From: Göran Andersson
- VB.Net Rules!
- Prev by Date: Can't understand why code saying column doesn't belong to DataTable
- Next by Date: Re: Designer shows combobox but run time does not
- Previous by thread: Re: VB.Net Rules!
- Next by thread: Re: VB.Net Rules!
- Index(es):
Relevant Pages
|
