**** BEGIN LOGGING AT Mon Jul 13 02:59:59 2015
Jul 13 20:07:23 <GodGinrai> Hey dmanderson, I just noticed the "allowHighlanderDeactivate" property in enyo.Group.  Maybe it should be renamed to "thereCanBeNone" :P
Jul 13 20:11:57 <dmanderson> lol nice
Jul 13 20:35:51 <GodGinrai> doing all this React coding really has me wanting to code something in Enyo... <.<
Jul 13 20:39:51 <dmanderson> hahaha
Jul 13 20:56:00 <GodGinrai> God, I can't even easily add a class to my child components using react T_T
Jul 13 20:57:01 <chall> I refuse to learn React
Jul 13 20:57:24 <GodGinrai> chall: you can't refuse to learn it when your job requires it
Jul 13 20:57:27 <chall> like Angular, it'll be replaced by something next year
Jul 13 20:57:33 <chall> fair enough
Jul 13 20:57:44 <chall> I get to be part of those kinds of decisions, so...
Jul 13 20:58:01 <GodGinrai> React has a better foundation than Angular, so I don't think it's going away any time soon
Jul 13 20:58:12 * chall shrugs
Jul 13 20:58:18 <chall> Angular was pretty popular
Jul 13 20:58:28 <chall> and made by Google, I don't think you can get much better than that
Jul 13 20:58:55 <chall> I think Polymer is going to get you a lot farther than anything else
Jul 13 21:04:20 <GodGinrai> except it wasn't made by google
Jul 13 21:04:26 <GodGinrai> and it flew against standards
Jul 13 21:16:13 <chall> According to the Angular page "Super-powered by Google ©2010-2015"
Jul 13 21:16:24 <chall> certainly looks like it was developed by Google
Jul 13 21:16:57 <chall> https://angularjs.org/img/AngularJS-large.png
Jul 13 21:17:06 <GodGinrai> "made by Google" and "one of the key devs who created it started working at Google" are not the same thing
Jul 13 21:17:08 <chall> it even says "By Google" right in their header
Jul 13 21:17:30 <GodGinrai> Google supports it now, sure
Jul 13 21:17:38 <GodGinrai> but it was not "made" by Google
Jul 13 21:18:56 <chall> I can't really argue that, but I don't really agree either
Jul 13 21:19:29 <chall> just because someone didn't start something doesn't mean they haven't been a majority share of its development
Jul 13 21:26:04 <GodGinrai> besides, I'm pretty sure that "By Google" stuff didn't show up until Angular 2.0 was unveiled (which breaks compat with Angular 1.0, so no one cares)
Jul 13 21:28:10 <dmanderson> Colorfull discussion :)
Jul 13 21:40:02 <chall> GodGinrai, be that as it may, it's still been owned by Google for 90% of it's existence, if that copyright is to be believed.
Jul 13 21:40:41 <chall> if that doesn't qualify enough as being "made by" them, I don't know what does
Jul 13 21:41:16 <GodGinrai> maybe
Jul 13 21:41:49 <GodGinrai> either way, React doesn't break standards like Angular does, so it's off to a better start
Jul 13 22:10:18 <GodGinrai> I hate that react ties a component's creation to its first render....
Jul 13 22:11:25 <GodGinrai> I can't do anything meaningful using the children before they've been rendered because of it
Jul 13 22:45:32 <Zectbumo> GodGinrai: so does that make you to do stuff like display:hidden until after you're done initializing the children?
Jul 13 22:46:29 <Zectbumo> er, visibility:hidden. I was going to say display:none, but that makes things jump around and then I changed my mind
Jul 13 22:52:31 <Zectbumo> I'm surprised Python isn't declared "made by Google" yet. Guido has been working for Google for some time now. He even has Google written all over him.
Jul 13 22:52:34 <Zectbumo> https://en.wikipedia.org/wiki/Guido_van_Rossum
Jul 13 22:54:26 <Zectbumo> wait what!? he works for Dropbox now. I've been under a rock.
Jul 13 23:05:21 <dmanderson> a big rock yea
Jul 13 23:05:23 <dmanderson> :-
Jul 13 23:05:25 <dmanderson> :-p
Jul 13 23:05:42 <dmanderson> So looks like there maybe some more resources thrown behind taking Enyo native.
Jul 13 23:14:03 <GodGinrai> Zectbumo: no, but it stops me from getting default values from the children and populating them in a list until after they have rendered
Jul 13 23:14:22 <GodGinrai> dmanderson: neat
Jul 13 23:17:18 <dmanderson> Way neat :)
Jul 13 23:44:48 <GodGinrai> dmanderson: will Enyo native need recompiles to work on different architectures?
Jul 13 23:45:16 <dmanderson> Qt does, but the JS wont.
Jul 13 23:45:55 <dmanderson> My PoC was mostly aimed at NodeJS, so WebOS is a natural target.
Jul 13 23:46:23 <dmanderson> With no NodeJS, and if we wanted to target Android/iOS we would need to look into a transpiler like react (or I prefer, to get enyo running on Qt JS)
Jul 13 23:47:00 <GodGinrai> dmanderson: so if Qt has already been recompiled for the target architecture, it should just work?
Jul 13 23:47:36 <dmanderson> Right
Jul 13 23:48:07 <GodGinrai> I'm wondering because I think it may be interesting to do some Enyo Native development for the Pyra handheld, which will be running Debian on a TI OMAP5
Jul 13 23:48:45 <dmanderson> Oh nice, would totally be able to target something like that
Jul 13 23:48:52 <GodGinrai> cool
Jul 13 23:49:15 <dmanderson> well see :) I still need to prove that it’s a worhty project to Enyo stake holders
Jul 13 23:49:23 <GodGinrai> hehe
Jul 13 23:49:23 <dmanderson> WebOS stake holders are convinced
Jul 13 23:49:58 <GodGinrai> Does it have any way to access the filesystem yet?
Jul 13 23:51:14 <dmanderson> There would be some unsandboxing of NodeJS done on webOS
Jul 13 23:51:21 <dmanderson> to make it more prominent in the app stack.
Jul 13 23:51:34 <dmanderson> But anything NodeJS would work in an Enyo Native App for webOS
Jul 13 23:51:40 <GodGinrai> I see
Jul 13 23:52:01 <dmanderson> Internally I’m pitching it as a way to have unified applcation development against a single API.
Jul 13 23:55:45 <GodGinrai> makes sense
**** ENDING LOGGING AT Tue Jul 14 02:59:58 2015