**** BEGIN LOGGING AT Thu Jun 11 02:59:59 2015 Jun 11 17:56:01 good morning Jun 11 18:04:40 morning Zectbumo Jun 11 18:27:25 :\ I wish Roy or dmanderson were here Jun 11 18:27:31 I have some questions about 2.6 Jun 11 18:28:17 what's new in 2.6? Jun 11 18:30:45 is it released ? Jun 11 18:31:28 Semanticfire: no, I'm just reading through the source to see the changes Jun 11 18:32:05 Zectbumo: lots. enyo.depends will be gone. You'll be using require or imports to import particular parts of enyo that you want Jun 11 18:32:21 ok Jun 11 18:32:56 it also looks like the global enyo object won't be around anymore, but I'm not sure about that one. I haven't looked through everything yet. Jun 11 18:33:49 Either way, migrating older apps to 2.6 will be a lot more work than migrating apps between previous versions Jun 11 18:34:20 what was wrong with depends? Jun 11 18:34:57 Zectbumo: well, for one, it limited how you could use Enyo. You needed a special build system to get it to work, and Enyo didn't like working with other systems like RequireJS Jun 11 18:38:16 I wouldn't be surprised if the 2.6 changes made it so that Enyo works in node without some weird hack Jun 11 18:45:09 it sounds like a whole lot of nothing that helps me and only causes me upgrade pain Jun 11 18:53:00 lol Jun 11 18:53:27 It will be an upgrade pain, to an extent Jun 11 18:53:36 however, I think that the benefits are worth it Jun 11 18:56:45 One worry I *do* have about 2.6 is that due to its flexibility, the way you might write your apps can possibly be less structured. Jun 11 18:57:42 I think I'm going to try messing around with it soon and see if I can't come up with a good format to propose for code snippets Jun 11 22:57:44 sugardave: any idea where all of the normal enyo team idlers are? **** ENDING LOGGING AT Fri Jun 12 02:59:59 2015