Daniel
Thu Mar 10 13:54:30 CST 2005
I agree and could easily add to your list... Naturally if all the people on
the CF team that worked on VB instead worked on C# and the framework and the
IDE, we would have a much better v1 product (with more features and without
the compromises made for VB's benefit).
The only problem with that is what you do with those that cannot do the evil
trio[1]. Your reply was that they should consider a different line of work.
Naturally MS opinion differs (they are their customers) hence where we are
now. Thanks for sharing.
[1] semicolons, braces and case sensitivity
Cheers
Daniel
--
http://www.danielmoth.com/Blog/
"Chris Tacke, eMVP" <ctacke@spamfree-opennetcf.org> wrote in message
news:Oc0GhQaJFHA.3752@TK2MSFTNGP14.phx.gbl...
> <again, just opinion>
> Those who averse to semicolons for the sake of aversion really should
> consider a different line of work. Staying with the old becasue of
> comfortability makes no sense to me. I started programming with VBA
> macros in Excel - when it became constraining on my needs, I evolved. We
> seem to have gotten rid of line numbers and eveyone seems to have
> survived, right?
>
> I guess my point is that I think VB.NET was a waste of MS resources that
> could have been better spent doing all those things that have slipped. I
> think it was purely as a marketing decision, to lull VB developers into
> some sense of security that what they knew was directly portable. The
> reality is that most of them had to learn a new method of thinking -
> essentially learning a new language anyway.
>
> Do I consider VB developers "below" C# developers? Not at all. I think
> it's about time they learned OOP and I applaud the fact that VB.NET didn't
> try to allow otherwise. I just dislike the fact that VB seems to have had
> influence in areas that it shouldn't have, for technical reasons I can't
> understand. I mean really, why did the CLR make unsigned numbers
> non-compliant, if not to only make VB developers comfortable? What other
> language doesn't have unsigned numbers? I mean when VB devs need to use
> the MSB of a flag DWORD, they now have to understand twos-complementing.
> Seems to me learning how to use an unsigned number is simpler.
>
> Other examples of the disparity abound. Look at XML documentation.
> Someone had to spend time to write the tool to allow VB to get what C#
> already had. Look at control design. If there had been only 1 language to
> target, maybe we would have gotten designer support for controls or other
> important yet missing items in CF 1.0 because the Studio and CF teams
> wouldn't have been burining time supporting 2 languages.
>
> </again, just opinion>
>
> --
> Chris Tacke
> Co-founder
> OpenNETCF.org
> Has OpenNETCF helped you? Consider donating to support us!
>
http://www.opennetcf.org/donate
>
>
> "Daniel Moth" <dmoth74@hotmail.com> wrote in message
> news:efBb%233ZJFHA.2956@TK2MSFTNGP12.phx.gbl...
>> Chris, please allow me a genuine question on your opinion:
>>
>> For better or for worst there are those that cannot stomach semicolons,
>> braces and case sensitivity (I am not one of them but I *know* they
>> exist).
>> Do we force them to just put up or give up?
>>
>> Just curious... ...and to contribute something other than a question to
>> the thread: unsigned numbers are available in CF 2.0 :-)
>>
>> Another appreciable difference IMO is custom control creation (C# only).
>>
>> Cheers
>> Daniel
>> --
>>
http://www.danielmoth.com/Blog/
>>
>>
>> "Chris Tacke, eMVP" <ctacke@spamfree-opennetcf.org> wrote in message
>> news:%23fgC9rLJFHA.3336@TK2MSFTNGP10.phx.gbl...
>>> Neither is better than the other. The only appreciable difference is
>>> the
>>> availability of unsafe in C#.
>>>
>>> <opinion>
>>> VB.NET was a waste of time to create, as it's totally different than
>>> VB6,
>>> so if you have to learn a new language, learn C#.
>>> VB.NET was likely a product of marketing more than engineering. It
>>> ended
>>> up confusing more people than it helped and it strapped the CLR with
>>> stupid problems (like the inability to use the very useful and necessary
>>> unsigned numbers).
>>> </opinion>
>>> --
>>> Chris Tacke
>>> Co-founder
>>> OpenNETCF.org
>>> Has OpenNETCF helped you? Consider donating to support us!
>>>
http://www.opennetcf.org/donate
>>>
>>>
>>> "Philip Germanos" <PhilipGermanos@discussions.microsoft.com> wrote in
>>> message news:F14B99D7-0435-4E82-A555-E4A76720EA12@microsoft.com...
>>>> Hello.
>>>> I have a project which consists of developing an application for pocket
>>>> pc's.
>>>> Briefly the client application which is a medical application for
>>>> pharmacists will have to access a database server for data retreival.
>>>> Its the first time i am getting in touch with .Net development, so
>>>> what's
>>>> the difference between C# and Visual Basic.Net and which one of them
>>>> should i
>>>> use?
>>>> And by the way, which way is better, a two tier architecture with a
>>>> client
>>>> application on the pocket pc's accessing the database server directly,
>>>> or
>>>> a
>>>> three tier architecture with a server application in between the client
>>>> and
>>>> the database?
>>>> Thank you.
>>>
>>>
>>
>
>