我一段一段翻译，一段话一层楼。
先翻译 Mads Torgersen 的《.NET 语言策略》，然后翻译 VB team 的《深入挖掘VB语言策略》。
如果遇到插楼，请使用只看楼主。
完结之后麻烦大吧加个精，让更多人看到 VB 的未来规划。
_

The .NET Language Strategy
.NET 语言策略
I am constantly aware of the enormous impact our language investments have on so many people’s daily lives. Our languages are a huge strength of the .NET platform, and a primary factor in people choosing to bet on it – and stay on it.
我一直认为到我们的语言投资对许多人的日常生活产生了巨大的影响。我们的语言是 .NET 平台上的巨大的力量, 是人们选择下注并留下的主要因素。
_

I’ve been here on the .NET languages team at Microsoft for more than a decade, and I’ve always seen us have developers’ interests first and foremost in our minds as we moved the languages forward. The open source revolution (of not just the .NET languages but the HYPERLINK "https://github.com/dotnet/" whole .NET stack) has improved the conversation dramatically, and – I think – helped us to make better choices. However, we haven’t always been good at sharing how we make those decisions: Our language strategy; the framework for how we think about each of our .NET languages and chart their evolution.
我已经在微软的 .NET 语言团队工作十几年，微软的 .NET 语言团队已经超过十年了, 我一直看到, 当我们向前推进语言时, 我们首先在头脑中有开发者的兴趣。开源革命 (不仅仅是 .NET语言, 而是整体 .NET 栈 ) 大大改善了对话, 我认为这帮助我们做出更好的选择。然而, 我们并不总是善于分享我们如何做出这些决定: 我们的语言策略;我们如何看待我们每个人的框架. net 语言和图表的进化。
_

This post is meant to provide that additional context for the principles we use to make decisions for each language. You should consider it as guidance, not as a roadmap.
这篇文章是为了为我们使用为每种语言做决定的原则提供额外的上下文。你应该考虑它作为指导，而不是一个路线图。
_

Visual Basic is used by hundreds of thousands of people. Most are using WinForms to build business applications in Windows, and a few are building websites, overwhelmingly using ASP.NET Web Forms. A majority are also C# users. For many this may simply be because of language requirements of different projects they work on. However, outside of VB’s core scenarios many undoubtedly switch to C# even when VB is supported: The ecosystem, samples and community are often richer and more abundant in C#.
Visual Basic 是成千上万的人使用的。大多数人使用 winforms 来在 windows 中构建业务应用程序，而一些网站则使用 asp.net web 窗体来构建绝大多数的站点。多数人也是 c# 用户。对于许多人来说, 这可能只是因为他们所从事的不同项目的语言要求。然而, 在 VB 的核心方案之外, 许多人毫无疑问地切换到 c
# 哪怕VB支持︰（因为） 生态系统、样本和社区在 c#
中往往更丰富
_

An interesting trend we see in Visual Studio is that VB has twice the share of new developers as it does of all developers. This suggests that VB continues to play a role as a good, approachable entry language for people new to the platform and even to development.
我们在 visual studio 中看到的一个有趣的趋势是, 相对于所有开发人员, VB 有两成新开发人员份额。这表明, VB 继续扮演一个好的, 平易近人的入门语言平台, 甚至是开发（平台）。
_

The Stack Overflow survey is not kind to VB, which tops the list of languages whose users would rather use another language in the future. I think this should be taken with several grains of salt: First of all this number may include VB6 developers, whom I cannot blame for wanting to move on.
Stack Overflow调查对 VB 不友好, 就是用户想在未来使用的语言的列表。我想这应该要用半信半疑的态度对待: 首先, 这个数字可能包括 VB6 开发商, 我不能责怪他们想继续前进。
_

Also, Stack Overflow is not a primary hangout for VB developers, so if you’re there to even take the survey to begin with, that may be because you’re already roaming Stack Overflow as a fan of another language. Finally, a deeper look at the data reveals that the place most VB developers would rather be is C#, so this may be more about consolidating their .NET development on one language, and less of a rejection of the VB experience itself.
另外, Stack Overflow不是 VB 开发人员的主要聚集地, 因此, 如果您甚至在那里开始进行调查, 那可能是因为您已经是漫游在Stack Overflow中另一种语言的粉丝。最后, 对数据进行更深的观察, 揭示了大多数 VB 开发人员宁愿待的地方是 c#（社区） , 因此可能要关于进一步整合它们（译者注：社区资源）. 减少对 VB 体验本身的排斥。
_

All that said, the statistic is eye opening. It does look like a lot of VB users feel left behind, or are uncertain about the future of the language. Let’s take this opportunity to start addressing that!
综上, 统计是眼界开放的。它看起来像很多 VB 用户觉得落后, 或者是不确定未来的语言。让我们借此机会着手解决这个问题!
_

We will keep Visual Basic straightforward and approachable. We will do everything necessary to keep it a first class citizen of the .NET ecosystem: When API shapes evolve as a result of new C# features, for instance, consuming those APIs should feel natural in VB. We will keep a focus on the cross-language tooling experience, recognizing that many VB developers also use C#.
我们将保持Visual Basic直观和平易近人。我们将尽一切所需, 使它成为一个一流的.NET 生态系统公民: 当 API 形式由于新的 C# 功能而演化时, 例如, 使用这些 API 时, 在 VB 中会感到很自然。认识到许多 VB 开发者也使用 C#，我们将着重于跨语言工具体验。
_

This is a shift from the co-evolution strategy that we laid out in 2010, which set C# and VB on a shared course. For VB to follow C# in its aggressive evolution would not only miss the mark, but would actively undermine the straightforward approachability that is one of VB’s key strengths.
这是我们在一年中制定的共同进化战略的转变, 就是在共享课程上设置了 c
# 和 vb。对于 vb 在其侵略性进化中遵循 c#
, 不仅会错过标记, 而且会积极地破坏是 vb 的关键强项之一的平易近人。
_

介绍VB14和VB15的我之前发过帖子，跳过这些，不翻译了。
_

Digging Deeper into the Visual Basic Language Strategy
深入了解VB语言策略
Today Mads made HYPERLINK "https://blogs.msdn.com/dotnet/2017/02/01/the-net-language-strategy" an excellent post about our overall .NET Language Strategy. As I know this will raise a lot of questions in the VB community I wanted to take an entire post on the VB team blog to dive deeper into how VB fits into that strategy and why and what that means in practical terms for us as a community.
今天 Mads 发了一个出色的帖子描述 .NET 语言策略。我知道这会在 VB 社区引发很多问题, 我想在 VB 团队博客上发一个完整的帖子, 来深入了解 VB 如何适应这一战略, 以及为什么这意味着我们作为一个社区的实际意义。
_

向回看
Six and half years ago, the Visual Studio Languages team laid out the motivations for our then-new co-evolution strategy. Mainly the significant overlap in adoption between VB and C# in adoption and use cases and four “powerful unifying forces” they shared:
六年半年前, visual studio 语言团队为我们的新的共同进化战略奠定了动力。主要意义在使用 VB 和 C# 之间的重要重叠, 它们共有四个 "强大的统一力量":
·The common IDE and platform building blocks that VB and C# share.
·The shared “multi-paradigm, object-oriented, imperative, strongly-typed, etc.” natures of the languages.
·The need for strong inter-language interoperability and the trend for the richest language innovation opportunities to be at the boundaries of APIs (e.g. Generics, LINQ, Async).
·Customer feedback on language tooling parity.
·用 VB 和 C# 共享的通用 ide 和平台构建块。
·共享的 "多范型、面向对象、命令式、强类型等" 语言的性质。
·在 API 的边界需要强大的中介语互操作性和最丰富的语言创新机会的趋势 (例如泛型, 语言集成查询, 异步)。
·客户反馈语言工具奇偶校验。
_

What’s Changed?
有何变化？
In 2010, the four “powerful unifying forces” laid out were the dominant forces acting on our two largest languages and they acted on them in roughly the same way. Those four forces are still relevant, though no longer the dominant drivers of growth and innovation for .NET, the languages, or the language communities. Since 2010 several new forces have become major players in our ecosystem and they influence our languages very differently
2010 年，四个 "强有力的团结力量" 是以我们两种最大的语言行事的统治势力, 他们以大致相同的方式行事。虽然不再是增长和创新的主要推动力. net、语言或语言社区, 这四个力量仍然是相关的。自今年以来, 一些新的势力已经成为我们生态系统的主要角色, 他们对我们的语言产生了很大的影响。.
_