选择正确的技术和环境
我们是两位即将开始新网络产品开发的开发人员。
我们都是精益创业方法的粉丝，并且愿意实践持续部署。
困境来了——我们都是C#/Windows背景，我们需要在两者之间做出选择：
坚持.NET和Windows，我们不会浪费时间学习新技术，而是把所有的精力都放在开发上。
切换到 Ruby on Rails 和 Linux，它们因快速启动和广泛的开源支持而享有盛誉。不利的一面是，我们需要投入大量精力来学习 Ruby、Rails 和 Linux...
你会怎么做？ 我们还应该考虑哪些其他因素？
We are two developers on the edge of starting new web product development.
We are both fans of lean start-up approach and would like to practice continuous deployment.
Here comes the dilemma - we are both coming from a C# / Windows background and we need to decide between:
Stick to .NET and Windows, we will not waste time on learning new technologies and put all our effort in the development.
Switch to Ruby on Rails and Linux which has a good reputation of fast ramp up and vast open source support. The negative side is that we will need to put a lot of effort in learning Ruby, Rails and Linux...
What would you do?
What other considerations should we take?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
一定要坚持你所知道的，花时间解决领域问题而不是学习新技术（特别是你们都没有 Ruby 经验）。
除非您相信 Ruby 可以为您提供 .NET 无法提供的东西，并且从长远来看您将节省时间并更快地将您的产品推向市场？
我认为主要考虑的是上市时间以及没有收入你能活多久？
为了速度，您可以决定在 .NET 中执行 V1，并计划在 Ruby 中执行 V2。
我经常发现，将产品快速推向市场，看看真实用户的意见，改变产品等等，比拘泥于技术更有用。
Surely stick to what you know, and spend your time solving the domain problems and not learning new technology (especially as neither of you have experiance in Ruby).
Unless you believe that Ruby can offer you something that .NET cannot and in the long term you will save time and get your product to market quicker?
I think the main consideration is time to market and how long you can live without revenue?
You could decide to do V1 in .NET for speed and plan V2 in Ruby.
I often find that getting a product out to market quickly and see what real users say, changes the product etc.. and is more useful than getting stuck on technologies.
在做出此类决策时，许多因素都会发挥作用：时间和预算限制，以及技术组合中的学习曲线深度。语言和平台与你的开发方法和市场策略关系不大。
A lot of factors come into play when it comes to decisions like this: time and budget constraints, plus depth of learning curve in your technology portfolio. The language and platform has less to do with your development methodology and market strategy.