Angular 2 vs KnockoutJS: What are the differences?
Angular 2 and KnockoutJS are both open source tools. Angular 2 with 49.5K GitHub stars and 13.5K forks on GitHub appears to be more popular than KnockoutJS with 9.54K GitHub stars and 1.54K GitHub forks.
AgoraPulse, WePay, and Edools are some of the popular companies that use Angular 2, whereas KnockoutJS is used by Runscope, Huddle, and EasyPreOrders. Angular 2 has a broader approval, being mentioned in 259 company stacks & 237 developers stacks; compared to KnockoutJS, which is listed in 27 company stacks and 21 developer stacks.
I was first sceptical about using Angular over AngularJS. That's because AngularJS was so easy to integrate in existing websites. But building apps from scratch with Angular is so much easier. Of course, you have to build and boilerplate them first, but after that - you save a ton of time. Also it's very cozy to write code in TypeScript.
It is a complete waste of time and life to learn a different framework to solve the same problem (Both AngularJS and Angular build A+ UI's, but both require a lot of time to learn). It's dumb to spend 200 hours learning AngularJS, then 200 hours learning Angular when you could spend 200 hours learning AngularJS and 200 hours learning how to solve a different problem (like AI/ML, Data Science, AR/VR, Digital Marketing, etc.)
When deciding on a front end framework to build my bitcoin faucet project, I knew I needed something battle hardened, dependedable, but also feature filled and ready to go out of the box.
While I've written some smaller apps with ng2+, I've never gone full tilt with it so I knew there were still some things to learn, and most importantly: how to do them properly, such as proper component architecture and breaking old habbits from ng1.
I didn't opt for React in this case, simply due to the need to stack more and more things on top of it to do what I'd need it to do. I wanted a framework that was going to take over routing and execution of complex UI controls, and keep items outside of a component's scope updated and react to events. This framework needed a comprehensive event emission system, data acquisition and handling, bi-directional data binding, state, and a series of things that you'd need to install separately for React to match up to what's already in the box with Angular.
I opted to stick to Angular instead of Vue for the fact that Angular also already has it's entire build system ready to go and comprehensivly built to deliver the tiniest version of it's deliverable. I was hosting this thing in a google cloud instance, so I needed to make sure the app stayed as small as possible, and could automatically trim out the cruft. This is where Angular's built in Tree Shaking took precedence for me.
Vue is more than capable of handling everything I'd need, and it was something I took serious considerion of. For instance, Vue poweres Cointiply, another bitcoin faucet application that's highly reactive and high componentized just like I wanted.
But I'd still need to learn Vue, I'd still need to configure it's build system, and I still wanted to use SCSS and TypeScript.
So Angular it was. ng8 is a great platform for building very complex user interfaces, and has many of the problems you'd inevitably face integrating a user interface to an application already figured out, and complete with a best practice recommendation.
React and Vue, given enough time and energy, are super capable platforms. No one can deny that. Angular's "A-Z Batteries Included" approach to the whole development process is what made it especially enticing this time.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Angular 2?
What is Knockout?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
The Angular 2 CLI is great, it's easy to get up and running with a project.
The really great thing about Angular 2 is it allows us to work with designers by augmenting their artifacts (html pages) with Angular directives. This allows our designs to go back and forth between designers and engineers without having to learn a new markup language (like JSX).
Angular 2 is a great framework for C# developers. Deeply rooted in OOP & MVC principles and full integration with TypeScript. My go-to for client-side dev now...
Angular 2 is a beautiful and fast MVC Framework. We are using it for mobile, web and desktop development.