Is there a reason I would use Knockout MVC instead of Knockout JS?

Is there a reason I would use Knockout MVC instead of Knockout JS?

Asked on November 16, 2018 in knockout js.
Add Comment


  • 3 Answer(s)

      Knockout MVC is the poor  WebForms. It routes all viewmodel methods through user control, meaning everything that happens come to server and back.Try a framework like knockout, which is intended to be CLIENT SIDE MVVM, and Make it to run the server for all function.

      Plus, working this in server denotes the whole viewmodel needs to be passed to the server, and back to the client, for every function call. This is useless.

      Using Knockout MVC equal to waste performance benefits of client-side code for the good of not having to write javascript. The same trade-off WebForms made.

       If Knockout MVC is not there, the web will be a better.

    Answered on November 16, 2018.
    Add Comment
    • If the functions is not used which is generated by komvc ,the performance is remain there.
    • The first page generation would still have to be server generated.
    • Add user scripts and make functions on the client side that won’t need to return to the server.
    • This tool provide the developer a bit of productivity. The comparison with web forms on work is sure exaggerated.
    Answered on November 16, 2018.
    Add Comment

       Use of knockoutjs is little good, though it is difficult to write compared to knockout MVC, the good is re-usability. The client code can perform  with other function as good.

       Apart from security view, knockout js is a way of complicating asp.net MVC and it is good to use with pure applications such as asp.net webapi.

    Answered on November 16, 2018.
    Add Comment


  • Your Answer

    By posting your answer, you agree to the privacy policy and terms of service.