>> but isn't exploration and figuring things out a huge part of creating software
Absolutely, but each developer will make that judgement and require.js shouldn't be victims of those who give up at the first hurdle.
>> There are require.js examples apps on github , Q and As on Stackoverflow, and open source code that's available for digging deep
That's good to hear. I will at some point give it another shot and it's good to know there are examples and support out there. It was a couple of years ago when I did look into it, I remember getting confused and the on site documentation didn't really steer me in the right direction. The documentation doesn't appear to have changed much in that time. It can be hard work and time consuming having to dig deep to solve a problem.
>> Do they now have to upload the know how of these tools to the users brains in a Matrix like fashion?
The OSC are not obliged to provide a better user experience in getting new users to adopt their software. Of course not. But if they want to have as many developers appreciating their hard work, then you know, it doesn't hurt.
>> It only took me ~2 Days to get the gist of require.
2 days to learn how to use it is something I cannot afford for a workflow improvement over a show-stopper problem. If it was something I could do in a hour to get an understanding and start porting my application with the knowledge that I'm not going to be stuck for 2 days, then that would be a different situation.
Absolutely, but each developer will make that judgement and require.js shouldn't be victims of those who give up at the first hurdle.
>> There are require.js examples apps on github , Q and As on Stackoverflow, and open source code that's available for digging deep
That's good to hear. I will at some point give it another shot and it's good to know there are examples and support out there. It was a couple of years ago when I did look into it, I remember getting confused and the on site documentation didn't really steer me in the right direction. The documentation doesn't appear to have changed much in that time. It can be hard work and time consuming having to dig deep to solve a problem.
>> Do they now have to upload the know how of these tools to the users brains in a Matrix like fashion?
The OSC are not obliged to provide a better user experience in getting new users to adopt their software. Of course not. But if they want to have as many developers appreciating their hard work, then you know, it doesn't hurt.
>> It only took me ~2 Days to get the gist of require.
2 days to learn how to use it is something I cannot afford for a workflow improvement over a show-stopper problem. If it was something I could do in a hour to get an understanding and start porting my application with the knowledge that I'm not going to be stuck for 2 days, then that would be a different situation.