火花或不星火？ [英] To Spark or not to Spark?

问题描述

一直在一个巨大的学习热潮与ASP.MVC 2还很少，最近发现有不同的渲染引擎有...星火特别引起我的注意，两件事情虽然。

1. 我有丰富的专业知识与ASP.NET所以它是值得的斜升，除了ASP.NET MVC


2. 是否值得有什么看法？真的有关系吗？这似乎是一个品味preference确确实没有那么多的表现还是在开发时间甚至大幅减少。


3. 这似乎仍然不成熟，不能很好的支持智能感知，语法高亮支持，没有太多的工具选项。它有MVC 2 preliminary只支持...

你有什么想法？我倾向于它可能不值得...

解决方案

在回答这三个部分的问题，以便...

1. 这可能是学习，每次新的东西是个好主意。特别是因为几乎所有的MVC例子和教程将在WebForms的语法。这就是说 - 这是最好的一个实验的解决方案，而不是你的真实的项目学习，这样以后你觉得你有MVC概念下它是创建一个新的沙箱，并尝试一些MVC +星火页面是一个好主意。




2. 性能的内存pressure或者处理器使用率而言可能并非对所有的最重要的考虑，但最大的网站...对开发商的影响，和设计师/创意，时间可能小在第一，但它的累积和非线性。简化了前端将节省您的痛苦的容载量在未来，简单，朴实的语法的位星火视图引擎premise的基石。




3. 这是非常真实的。经验的抛光和细化工具和现代的IDE的最昂贵的部分。我想这就是为什么大多数OSS网络堆栈与一个伟大的编辑器启动（咳嗽的TextMate中的咳嗽的），并从那里工作的方式了。火花，你可以得到CSharp语言智能感知，但是这显然是工具支持的低水位。

这是传闻，但是衡量一种方法是许多人后悔如何使用Spark和切换回来。我不知道很多 - 虽然在获得MVC 2的支持了延迟出了大门，有一些人想知道，我敢肯定，

。

Been on a huge learning binge with ASP.MVC 2 lately, and recently uncovered there are different rendering engines out there... Spark especially caught my attention, couple of things though.

1. I have vast knowledge with ASP.NET so is it worth the ramp up, in addition to ASP.NET MVC
2. Is it worth it in general? Does it really matter? It seems to be a preference of taste really and not so much performance or even a substantial reduction in developer time.
3. It still seems immature, not very good intellisense support, syntax highlighting support, not many tooling options. It has preliminary support for MVC 2 only...

What are your thoughts? I am leaning towards it's probably not worth it...

解决方案

Answering the three part question in order...

1. It probably is a good idea to learn new things one at a time. Especially because nearly all of the MVC examples and tutorials will be in WebForms syntax. That said - it's best to learn in an experiment solution rather than your "real" project, so after you feel like you have MVC concepts down it's a good idea to create a new sandbox and try a few MVC + Spark pages.

2. Performance in terms of memory pressure or processor utilization probably isn't the most important consideration for all but the largest web sites... The impact on developer, and designer/creative, time may be small at first but it's cumulative and non-linear. A bit of simplification up front will save you boatloads of pain in the future, and "simple, plain syntax" is the cornerstone of Spark view engine premise.

3. That is very true. The polish and refinement of experience is the most expensive part of tooling and modern IDE's. I think that's why most OSS web stacks start with a great editor (cough TextMate cough) and work their way up from there. With Spark you can get csharp language intellisense, but that's clearly the low water mark for tooling support.

It's anecdotal, but one way to measure is how many people regret using Spark and switch back. I'm not sure of many - though the delay out of the gate in getting MVC 2 support out had some people wondering, I'm sure.

这篇关于火花或不星火？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！