是VB.NET开发那么好奇？标准化的VB.NET [英] Are VB.NET Developers Less Curious? Standardizing on VB.NET
问题描述
我问这个问题的人谁的公司与一个70％至75％VB.NET开发者社区。我会说80％的开发人员不知道什么是OOD模式。我想知道，如果这是我公司的发展努力的健康的最好的事情？
I'm asking this question as someone who works for a company with a 70% to 75% VB.NET developer community. I would say 80% of those developers do not know what an OOD pattern is. I'm wondering if this is the best thing for the health of my company's development efforts?
我看的标签数：
http://stackoverflow.com/tags
目前有：
12175 .NET问题
18630 C＃的问题
2067 VB.NET问题
I'm looking at the tag counts on:
http://stackoverflow.com/tags
There are currently:
12175 .NET questions
18630 C# questions
2067 VB.NET questions
检查亚马逊，好像有：
51 C＃Wrox图书
21 VB.NET Wrox图书
Checking Amazon, it seems like there are:
51 C# Wrox books
21 VB.NET Wrox books
在codePLEX有：
979项目标记C＃
136项目标记VB.NET
On CodePlex there are:
979 Projects tagged C#
136 Projects tagged VB.NET
肯定是有少看，如果你想成为一名VB.NET开发人员的学习材料。 什么是公司的优势，以标准化的VB.NET和招聘VB.NET开发？ Microsoft如何回答这个问题？
There is definitely less materials to learn from if you wanted to be a VB.NET developer. What would be a company's advantage to standardizing on VB.NET and hiring VB.NET developers? How does Microsoft answer this question?
是只有两个参数：
- 我们有这些VB6的程序员，并让让他们舒服
- XML文本
如果你工作的公司已经在VB.NET完全标准化，可您发布的答案解释他们为什么做了这个选择的务实的或技术的原因？
If you work for a company that has completely standardized on VB.NET, can you post an answer explaining the pragmatic or technical reasons why they made that choice?
更新：
更多统计 - O'Reilly的雷达
计算机图书市场2008 状态，部分4 - 该语言
UPDATE:
More stats - O'Reilly Radar
State of the Computer Book Market 2008, part 4 -- The Languages
推荐答案
我敢肯定大部分时间的原因，公司的前进与VB.NET是完全按照你提到的 - 在组织中大量的维生素B6，无论是在术语codeBase的和开发人员。请记住，ASP网站和VB6应用程序迁移到VB.NET几乎没有疼痛。 VB6到C＃是一个不同的故事。
I'm sure most of the time the reason companies go forward with VB.NET is exactly as you mentioned - large amounts of VB6 in the organization, both in terms of codebase and developers. Keep in mind that ASP websites and VB6 applications can be migrated to VB.NET with little to no pain. VB6 to C# is a different story.
话虽这么说，在已经使用VB.NET的公司工作过，有真正的你是怎么做的事情和开发商谁的在的好奇习惯阅读的例子，书籍等的差异很小在C＃。它不象它的几率非常难翻译C＃code到VB.NET，特别是如果你不能复制粘贴。
That being said, having worked at companies that have used VB.NET, there's really very little difference in how you do things and developers who are curious get used to reading examples, books, etc. in C#. It's not like it's terrifically hard to translate C# code to VB.NET, especially if you're not copy-pasting.
这篇关于是VB.NET开发那么好奇？标准化的VB.NET的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
