[batoure]

>I made a github issue about it, and the devs acknowledged the issue, saying it was no longer part of angular 2.0

Ok so I read all both of your other articles and found them to be interesting. I was disappointed that there wasn't some kind of afterword to go with the sabre rattling. Seeing that you put in an issue makes me feel alot better about the whole series.

As I read these I kept thinking... yeah but... and then thinking of a feature that annoyed me that changed from release to release.

And ultimately I think the biggest thing I have always liked about angular is how quickly the community has learned from potential mistakes and shed chaff code....

[AdrianRossouw]

I was always going to need to put this into an issue, once I identified why it bothered me.

I think angular is really special because I can see it getting simpler. I almost never see that in software.

They have shown that they are willing to change, and I think that they have the right people in charge to do it.

I think you are going to see some serious changes for 2.0 though. Now they are on semver, stuff is going to have to shift pretty majorly between major releases. You can see some of that in angulardart already.

I look forward to it.

[batoure]

I'm also pretty excited to see the next release.

I have read about potentially including lazy loading in the base which personally would be really huge. Not having to integrate Require would be a pretty interesting to me if it happens

[AdrianRossouw]

have you met my friend [1] browserify?

I'm probably not the audience for require.js, because I've never had a situation where I was forced to not have a build step. Once you just accept that there's always a build step, life becomes so much easier.

[1] http://daemon.co.za/2014/03/subtly-meta-introduction-to-brow...

[batoure]

>Once you just accept that there's always a build step, life becomes so much easier.

Sigh... but I don't want there to be a build step... :(

[AdrianRossouw]

I feel for you man. I really recommend you just try to build something, even if it's a little demo of some sort, with the assumption that you are going to have a build step.

I just found that the result of that assumption ends up with something that is a lot easier to work with and reason about, than trying to rail against it by using something like r.js.