News for hackers. Stuff that matters.
Re:Complexity Creeps: Why I'm Concerned for the Future of An... by batoure on Monday March 17, 2014 @06:46PM (#7418623)
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

Re:Complexity Creeps: Why I'm Concerned for the Future of An... by AdrianRossouw on Monday March 17, 2014 @06:56PM (#7418683)
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...

Re:Complexity Creeps: Why I'm Concerned for the Future of An... by batoure on Monday March 17, 2014 @07:05PM (#7418726)
>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... :(

Re:Complexity Creeps: Why I'm Concerned for the Future of An... by AdrianRossouw on Monday March 17, 2014 @07:42PM (#7418892)
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.