VB.Net正在超越C＃ [英] VB.Net is overtaking C#

问题描述

这个新闻组在一年左右的时间里比C＃小组活跃得多。

前。但在过去的几个月里，它的流量更大。我的理论是，最初有更多的C＃人，因为：


1.很多Java人都渴望出路

2.一般来说，C ++程序员更有可能成为新的
技术（点网）的先行者，因此C＃

3. VB6和经典ASP代码刚刚开始被移植，因此，

VB.Net刚刚开始建立势头。


总的来说我预测VB.Net使用得更广泛。在我们的商店里，我已经看到了已经看到C ++和Java家伙转换为VB.Net的原因，因为它更有效。$ div $ = h2_lin >解决方案

当然同意。过去，VB6是一个玩具。语言，不值得

站在C ++程序员precesnse。即使他们花了他们一个星期的时间，我们也会花一个小时与我们的花花公子VB6一起做。


现在，VB6确实有它的问题，但很容易阅读和理解。并且现在有了一个OO风格的
它对ol的c ++程序员更加友好。


仍然可以在文档上做得更好。另外，我喜欢在C＃中如何使用b $ b你似乎为了更好地控制你的事件（添加和删除

例子，我还没想出如何在VB.NET中自定义那些）。但是

否则我已经想要的一切在VB.NEt已经成为可能。并且

可读。 =）


{}当它们中有13个嵌套在方法中时会有点难以阅读。


-cJ

" vb" < [e-mail]>在消息中写道

news：9l ******************************** @ 4ax.com ...

这个新闻组在一年左右的时间里比C＃小组活跃得多。但在过去的几个月里，它的流量更大。我的理论是，最初有更多的C＃伙伴，因为：

1.很多Java人都渴望出路
2. C ++程序员更有可能一般来说，首先是一个新的技术（点网），因此C＃
3. VB6和经典的ASP代码刚刚开始被移植，因此，VB.Net刚刚开始建立势头。

总的来说，我预测VB.Net会被广泛使用。在我们的商店中，我已经看到C ++和Java人员转换为VB.Net因为它更有效率。

我认为它的马匹真的很棒。


我之所以选择VB.NET，是因为我不想学习C＃的内部以及

.NET框架。

一次性需要过多的脑力。


一旦我对这两者感到满意，我可能会尝试学习C＃


" CJ Taylor" <无**** @ blowgoats.com>写在消息

新闻：％2 **************** @ TK2MSFTNGP11.phx.gbl ...

同意课程。过去，VB6是一个玩具。语言，不值得站在C ++程序员precesnse。即使每周需要花费
，我们也会在一小时内与我们的花花公子VB6一起工作。

现在，VB6确实存在问题，但很容易阅读和理解。而且现在有了OO风格，它对ol的c ++程序员更加友好。

仍然可以在文档上做得更好。另外，我喜欢在C＃中如何看起来像为了更好地控制你的事件（添加和删除
例如，我还没想出如何在VB.NET中自定义那些）。但是，否则我想要的一切都是想要的。在VB.NEt已经成为可能。并且它的可读性。 =）

{}当有13个嵌套在
方法中时，有点难以理解。
-cJ

vb ; < [e-mail]>在消息中写道
新闻：9l ******************************** @ 4ax.com ... < blockquote class =post_quotes>这个新闻组在一年左右的时间里比C＃小组活跃得多。但在过去的几个月里，它的流量更大。我的理论是，最初有更多的C＃伙伴，因为：

1.很多Java人都渴望出路
2. C ++程序员更有可能一般来说，首先是一个新的技术（点网），因此C＃
3. VB6和经典的ASP代码刚刚开始被移植，因此，VB.Net刚刚开始建立势头。

总的来说，我预测VB.Net会被广泛使用。在我们的商店中，我已经看到C ++和Java人员转换为VB.Net因为它更有效率。

> ...另外，我喜欢在C＃中如何

你看起来像为了更好地控制你的事件（添加
并删除例如，我还没想出如何在

VB.NET中自定义那些）。


你熟悉AddHandler和RemoveHandler吗？

This newsgroup was much less active than the C# group a year or so
ago. But the last few months, its geting much more traffic. My
theory is that there were more C# folks at first, because:

1. Lots of Java guys were hungry for a way out
2. C++ programmers were more likely to be first-movers toward a new
technology (dot net) in general, thus C#
3. VB6 and classic ASP code just now starting to get ported, thus,
VB.Net just starting to build momentum.

Overall I predict VB.Net is much wider used. In our shop, I''ve
already seen C++ and Java guys convert to VB.Net because its more
productive.

解决方案

Agreed of course. It used to be that VB6 was a "toy" language, not worthy
to stand in a C++ programmers precesnse. Even though what would take them a
week we would do in an hour with our dandy VB6.

Now, VB6 did have its problems, but was easy to read and understand. And
now with a OO style its much more friendly to ol'' c++ programmers.

Still documentation could be better on something. Also, I like in C# how
you "seem" to have more control over your events (add and remove for
example, I haven''t figured out how to customize those in VB.NET yet). But
otherwise everything I''ve "wanted" to do in VB.NEt has been possible. And
its readable. =)

{ } get a little tough to read when there are 13 of them nested in a method.

-cJ
"vb" <[e-mail]> wrote in message
news:9l********************************@4ax.com...

This newsgroup was much less active than the C# group a year or so
ago. But the last few months, its geting much more traffic. My
theory is that there were more C# folks at first, because:

1. Lots of Java guys were hungry for a way out
2. C++ programmers were more likely to be first-movers toward a new
technology (dot net) in general, thus C#
3. VB6 and classic ASP code just now starting to get ported, thus,
VB.Net just starting to build momentum.

Overall I predict VB.Net is much wider used. In our shop, I''ve
already seen C++ and Java guys convert to VB.Net because its more
productive.

I think its horses for courses really.

I chose VB.NET because I didnt want to learn the intracies of C# as well as
the .NET framework.
just too much brain power needed in one go.

Once I get comfortable with the those two, I might try and learn C#

"CJ Taylor" <no****@blowgoats.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...

Agreed of course. It used to be that VB6 was a "toy" language, not worthy
to stand in a C++ programmers precesnse. Even though what would take them a week we would do in an hour with our dandy VB6.

Now, VB6 did have its problems, but was easy to read and understand. And
now with a OO style its much more friendly to ol'' c++ programmers.

Still documentation could be better on something. Also, I like in C# how
you "seem" to have more control over your events (add and remove for
example, I haven''t figured out how to customize those in VB.NET yet). But
otherwise everything I''ve "wanted" to do in VB.NEt has been possible. And
its readable. =)

{ } get a little tough to read when there are 13 of them nested in a method.
-cJ
"vb" <[e-mail]> wrote in message
news:9l********************************@4ax.com...

This newsgroup was much less active than the C# group a year or so
ago. But the last few months, its geting much more traffic. My
theory is that there were more C# folks at first, because:

1. Lots of Java guys were hungry for a way out
2. C++ programmers were more likely to be first-movers toward a new
technology (dot net) in general, thus C#
3. VB6 and classic ASP code just now starting to get ported, thus,
VB.Net just starting to build momentum.

Overall I predict VB.Net is much wider used. In our shop, I''ve
already seen C++ and Java guys convert to VB.Net because its more
productive.

>...Also, I like in C# how

you "seem" to have more control over your events (add and remove forexample, I haven''t figured out how to customize those in

VB.NET yet).

Are you familiar with AddHandler and RemoveHandler?

这篇关于VB.Net正在超越C＃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！