5 ms·

I remember that angular 2 thread. Half of the problems were the breaking changes between release candidates. I was one of those early adopters, pushing my code

by STRiDEX 10y ago

I remember that angular 2 thread. Half of the problems were the breaking changes between release candidates. I was one of those early adopters, pushing my code along between releases. It was bad, but nothing I didn't expect. They talked about the changes and explained the motives clearly. I think the problem is people want to be bleeding edge without joining the community. Edit: question for James. What did you build with angular 2? Is it public?

wmil 10y ago
I think that's something that hurt Ember.js early on. Their community was hyping each pre 1.0 RC / Beta but the public API was making breaking changes regularly. Too many devs got burnt.
thejameskyle 10y ago
> What did you build with angular 2? Is it public? Heh, I build the same thing every time because I am not creative. Here's the Marionette version: http://marionettewires.com/ http://marionettewires.com/ I could put it out there. The problem is that people assume when I share something that I am trying to tell them how things should be, like I'm some software design #thoughtleader genius. When really I'm just blindly trying to figure out what the hell I'm doing.