How Google broke the OSS compact with Angular 2.0

added by Paul Wheeler
10/28/2014 12:44:03 PM

271 Views

When I first wrote the title, I had to pause for a moment to consider if I was actually writing this post or if it was a bad dream. As it turns out, at least from my vantage point, what I’ve seen thus far, which candidly isn’t that much, has been much like a bad dream.


1 comments

Drew Peterson
10/30/2014 1:31:37 AM
Let's see, how many people can offend with this comment... ;-) This is the sort of thing that makes me glad I didn't pick Angular (but also sad that I picked Durandal, since Durandal vNext will be built on Angular 2.0). I don't know any of the folks working on Angular; I've heard a few of them speak on podcasts about it, that's the extent of my familiarity with them. My guess is that these folks would gladly spill their guts to anyone and everyone about what's coming, but I don't think they're allowed to. Keeping things under wraps like this screams of classic Google. By stark contrast, Microsoft has developed their entire next generation compiler, several languages, and many more projects led by MS Open Tech, et al completely out in the open. In 2014 that's how you must run an open source project. Open source is used by the biggest of the big and the smallest of the small. Fortune 500 companies pin their success on using free and open source software; untold number of startups have based their entire existence upon it. It cannot be successful if developed in a vacuum. It's important to avoid design by committee, but any project with a strong core team can avoid this problem by carefully reviewing/choosing/denying pull requests. I agree with John that Google must lift the curtain on Angular 2.0. What happens when companies invest time and money re-targeting Angular 2.0, only to be blind-sided by yet another rewrite with Angular 3.0?