Re: To Vb or not to VB
- From: "Dmitriy Antonov" <no@xxxxxx>
- Date: Thu, 21 Sep 2006 13:10:25 -0400
"Bob Butler" <tiredofit@xxxxxxxxxxx> wrote in message
news:%23HGW3nZ3GHA.4924@xxxxxxxxxxxxxxxxxxxxxxx
"Mitch5713" <mitch@xxxxxxxx> wrote in message news:45988AC2-37DA-45B9-
8625-5A9DEEDACAE9@xxxxxxxxxxxxx
I am looking for a few recomendations on the future of VB.
I am currently using VB5.0 and I understand both it an 6.0 are no
longer going to be supported. With this in mind what would be the
best platform to migrate to with these criteria::
You are in the same boat as *many* others and there really is no clear-cut
answer. If you can deal with Pascal then Delphi may be a good option. If
you are coding for yourself and not tied to a corporate environment then
RealBasic may be an option.
If you want to stay with MS products, and C++ is out, then I'd say the
only
reasonable choice would be C#; MS has demonstrated quite fully that they
consider VB to be disposable and I would not trust them to support VB.Net
in
any recognizable fashion but there *may* be longer-term support for C#
since
it's possible that they might actually use it themselves and therefore see
value in their own code assets which will protect yours.
Other opinions will differ. You need to weigh the alternatives and the
arguments pro and con for yourself. For me, VB.Net and VB200x and
whatever
comes after it are simply not options due to the (lack of) trust issue.
--
Reply to the group so all can participate
VB.Net: "Fool me once..."
I think that a choice between C# and VB.Net is more matter of taste and
previous experience. I am sure that one - two versions from now these will
be semantically identical by 99-100%. They already very close to each other
and working with one you can easily switch to another with a learning curve
in days or weeks. The most painful decision is whether to go to .NET at all
(having that mentioned trust issue). And if you answer yourself Yes then
choice between C# or VB.NET makes no much difference.
I would start with VB anyway - I still can use most of well-known for me VB
syntax and re-use many of professional habits. After getting experience with
VB.NET I would study C#. I think that an opposite direction is just
illogical.
Many times I saw opinion that similar but not exact syntax is a source of
confusion and as such it is better to use totally different syntax, having
C# in mind. But many of us use VB6 and VBScript, work with differences in MS
Access, MSSQL, Oracle and other dialects and extensions of SQL. Who wants
totally different Query Language for each DBMS just because two are not
precisely identical? No, having knowledge of language basic syntax is much
better start than studying new paradigm COMBINED with studying totally new
syntax. You once mastered suitable [for you] way of making indentations,
naming conventions, you like case-insensitivity for identifiers and many
other small, but important, details - why would you sacrifice it - you still
can re-use much of your knowledge and habits.
Dmitriy.
.
- Follow-Ups:
- Re: To Vb or not to VB
- From: cowznofsky
- Re: To Vb or not to VB
- References:
- Re: To Vb or not to VB
- From: Bob Butler
- Re: To Vb or not to VB
- Prev by Date: Allitcertkiller.com study guides now more cheaper than Realexamquestions.com
- Next by Date: Re: Microsoft Interop Forms Toolkit 1.0
- Previous by thread: Re: To Vb or not to VB
- Next by thread: Re: To Vb or not to VB
- Index(es):
Relevant Pages
|
