Why caliburn is not so common like prism? why there are only few who use caliburn? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 4 years ago.

开发者_如何转开发 Improve this question

I Don't understand this, its a good framework but not many use it.

If you know something I don't please help.

---

Because Microsoft made Prism and they are a lot of users who do not look beyond that.

---

I agree with bennage!

There are a silent revolution with Caliburn. We started using Caliburn 1,5 year ago, at that time the tutorials were few, and we had some problems finding the information we needed!

Today the amount of information and tutorials on Caliburn is much better than a year ago, but Caliburn is an open-source framework with all its normal pros and cons!

I know customers have shifted from MVVM Light to Caliburn due to limitations and problems with MVVM Light.

In my opinion Caliburn (and Caliburn Micro) is the best choice!

---

I have been looking into the same, and agree that Caliburn has a whole lot more features than MVVM Light or Prism, especially the auto binding properties/methods/View-VMs that you get in Caliburn, and Prism has too much overhead including configuring the Region Manager, Container, resolving/binding the VMs to the Views etc which we don't really need for our small application.

The main factor as rightly said above is the Prism is officially controlled and backed by Microsoft through its Microsoft Patterns and Practices Team. For the first years, it was exclusively controlled by them , and a new version of PRISM came out almost the same time as a new release of WPF/C#. It is now , however Open Source, but still a degree of control is maintained.

Caliburn started off as on Open source passion project to show a cleaner implementation of MVVM, and unfortunately, you always run the risk of such a project just losing interest and dying out after a while. That is a huge turning point.

However, something I can't really find is the differences between Caliburn and Caliburn Micro.

---

Change. People are afraid of it.

To add another dimension to this debate, some people that are used to the classical style of MVVM which is implemented in PRISM or MVVM Light are actually intimidated (scared ?) of the Magic Features and new conventions in Caliburn or Caliburn Micro. I know people on my team were very resistant to something that was new and different from what they knew already worked well enough for them.

This is perfectly understandable, I found it a little challenging to grasp it initially myself.

They can, however, take a look at Caliburn.Light

Caliburn.Light is another derivative/subtype of Caliburn. It removes some of the so-called "Magic" features, and instead adds some of the common features from Prism and MVVMLight. Sounds promising, but I haven't tried it myself.

Maybe this just needs better marketing (unlikely, cause free/open source) or at least a dedicated Dev Forum (This is where the MS ecosystem/userbase comes in). Prism has loads of both. Correct me if I'm wrong, but I haven't come across either for Caliburn.