How practical would it be to use Silverlight inside of an MVC view to achieve a GUI that's rather complex with Javascript (and crippling to non-usable without Javascript)?
I know nothing about Silverlight so if this seems like a good idea, how difficult would it be to do so, or vice-versa? Would asking users to install a plugin outweigh the differences in browser rendering of Javascript heavy UIs?
Tid bit more info: Although some would question the complexity of this View since it is virtually undo-able without Javascript, it's not that it's a complex page. It's a GUI that requires large selection lists and dynamic adding/removing. For example, the main list a user could choose from could easily grow to a size of 1000+ - something that is almost impossible to navigate without a search/easily navigable option. This is also something that needs to be a quick performable process by the user. For example, they select a variable number of items from a main list and then add a dynamic number of subitems to those items. Thus, spreading this out over multiple pages (for non javascript enabled users) would be extremely detrimental.