由网友(有网友问：有没有什么好听的微博名推荐一下。今天QQ乐园就为大)分享简介：此问题是由这个封闭的问题启发：This question is inspired from this closed question:What并棱镜实际上提供的开发者？而值得吗？ 我已经实现了自己的自定义MVVM实现企业应用。我想知道：I have already implemented my own custo...

此问题是由这个封闭的问题启发：

This question is inspired from this closed question:

What并棱镜实际上提供的开发者？而值得吗？

我已经实现了自己的自定义MVVM实现企业应用。我想知道：

I have already implemented my own custom MVVM implementations in enterprise applications. I am interested in knowing:

为什么要我学PRISM（具体PRISM，而不是其他MVVM框架）？ PRISM过定制MVVM实施和收益 是否值得学习PRISM投资？

我希望这个问题不是主观的，请大家不要陷入争论：）

I hope this question is not subjective and everyone please don't get into arguments :)

推荐答案

由于有许多框架，这样做的一个共同任务，你就得到：

As with many frameworks that do a common task for you, you get:

被更多的眼球测试：不仅仅是你自己。这（希望）包括单元测试，您可能会或可能不会进行，而构建自己的框架做的。 更多可读的其他开发：别人与您的自定义MVVM框架的经验。但是，如果另一个开发者加入您的项目，或者加入你的队伍，或者加入你的公司，他们可以直接跳转到棱镜code。 更好的文档：按照同样的思路，任何新的加盟可能已经从你的大脑，以及对球队的其他用户手工采集的集体知识学习的绳索，并通过查看来源$ C ​​$ C。第三方测试有其自己的文档，并在互联网上万吨以上的博客文章。 更好的社区：您可以提出问题上StackOverflow的关于？我怎么做X使用棱镜你不能要求与您的自定义框架。 可能的更强大：由需要服务不只是你/你的团队更多的用户，更多的功能将被添加。如果你需要做一些MVVM相关的，你从来没有做过，很可能是因为它不是建立在你自己的MVVM框架支持。但它可能在棱镜。 更好的结构：比方说，你想做一些MVVM相关，但它不在棱镜。很可能的是，有一个很好的理由！如果事情是没有在一个特定领域的工作做了一个（相当成熟）的框架，这是一个迹象，表明你正在尝试做的是接近问题的不自然或笨拙的方式。用自己的框架内工作，那太容易说哦，我要补充的是功能，那么6个月复查知道你犯了一个巨大的错误，因为这个新功能使您的code难以遵循，或最终被一个载体大量的漏洞，或诸如此类的东西。 简历行项目：实现和使用自定义的MVVM框架我将不得不对雇用谁曾有人感慨虽然这可能意味着，他们很聪明，它也可能表明了可怕的不在这里建综合征。在另一方面，把微软棱镜MVVM框架之间巨大的技术列表可能是好的，但不是哇儿。两个世界最好的将是一个较长的小点，线沿线的深刻理解MVVM模式，首先实施的玩具MVVM框架切换到MVVM棱镜之前学习的目的实现了。是的，这三者之间的区别是不会创造或打破你的简历，和不内置这里综合症是什么，将有望来在接受​​记者采访时，但它只是值得铭记，尤其是如果你申请为获得足够的简历，他们都不能扔掉任何东西，稍微unnerves他们的地方。 Tested by many more eyeballs: than just yourself. This (hopefully) includes unit tests, which you may or may not be doing while building your own framework. More readable for other developers: nobody else has experience with your custom MVVM framework. But if another developer joins your project, or joins your team, or joins your company, they can jump straight into Prism code. Better documentation: Along the same lines, anyone new joining likely has to learn the ropes by manually gathering the collective knowledge from your brain, and any other users on the team, and by looking at the source code. Third party frameworks have their own documentation, and tons more blog posts on the internet. Better community: You can ask questions on StackOverflow about "how do I do X with Prism?" You can't ask that with your custom framework. Likely more capable: by needing to serve more users than just you/your team, more features will have been added. If you need to do something MVVM-related that you've never done before, chances are support for it isn't built in to your own MVVM framework. But it's likely in Prism. Better structure: Let's say you wanted to do something MVVM-related but it wasn't in Prism. Very likely, there's a good reason for that! If something's not in a (reasonably-mature) framework made for working in a given domain, that's a sign that what you're trying to do is an unnatural or awkward way of approaching the problem. Working with your own framework, it's too easy to say "oh I'll add that feature," then 6 months later realize you made a huge mistake because this new feature makes your code very hard to follow or ends up being a vector for lots of bugs or whatnot. A CV line-item: I would have mixed feelings toward hiring someone who had "implemented and used custom MVVM framework." While it could mean they're smart, it could also indicate the dreaded "not built here syndrome." On the other hand, putting "Microsoft Prism MVVM Framework" among a huge list of technologies could be nice, but isn't a wow-er. The best of both worlds would be a longer bullet point, along the lines of "Deep understanding of the MVVM pattern, achieved by first implementing a toy MVVM framework for learning purposes before switching to MVVM Prism." Yes, the difference between these three isn't going to make or break your CV, and not-built-here syndrome is something that would hopefully come up in an interview, but it's just worth keeping in mind, especially if you're applying for a place that gets enough resumes they can afford to throw out anything that unnerves them slightly.