fluid-work IRC Logs-2013-10-03

Owned by Fluid IRC Log Bot
Last updated: Oct 03, 2013
5 min read

[12:13:40 CDT(-0500)] <colinclark> hey yzen

[12:13:48 CDT(-0500)] <yzen> colinclark: hi

[12:13:57 CDT(-0500)] <colinclark> you were mentioning liking debugging Node.js apps with eclipse

[12:14:11 CDT(-0500)] <yzen> colinclark: yes and it's pretty nice

[12:14:19 CDT(-0500)] <colinclark> Does it show any more than the 10 stack frames that node-inspector does?

[12:14:24 CDT(-0500)] <yzen> no (sad)

[12:14:34 CDT(-0500)] <yzen> it's not really node-inspector's setting

[12:14:38 CDT(-0500)] <colinclark> yeah

[12:14:40 CDT(-0500)] <colinclark> I know

[12:15:56 CDT(-0500)] <yzen> here's the page i used to set everything uphttps://github.com/joyent/node/wiki/Using-Eclipse-as-Node-Applications-Debugger

[12:16:16 CDT(-0500)] <yzen> you can also debug external node apps as well

[12:16:19 CDT(-0500)] <jhernandez> ** cough ** .. eclipse? really?

[12:16:33 CDT(-0500)] <yzen> jhernandez: isn't it awesome

[12:16:34 CDT(-0500)] <yzen> (smile)

[12:16:39 CDT(-0500)] <jhernandez> xDDD

[12:16:52 CDT(-0500)] <jhernandez> not for me but for others sure!

[12:16:57 CDT(-0500)] <jhernandez> (tongue)

[12:17:04 CDT(-0500)] <yzen> no kasparnet can not complaint that chrome crashes every time he's debugging

[12:17:09 CDT(-0500)] <yzen> he has no excuse any more

[12:17:13 CDT(-0500)] <jhernandez> haha

[12:17:57 CDT(-0500)] <yzen> Bosmon: you sitll use eclipse ?

[12:18:09 CDT(-0500)] <Bosmon> yzen - every day

[12:18:18 CDT(-0500)] <Bosmon> colinclark has been telling me about "what is now cool" in the node.js world : P

[12:18:22 CDT(-0500)] <yzen> Bosmon: nice so you ll find it handy

[12:18:36 CDT(-0500)] <colinclark> jhernandez: dude I'm with you

[12:18:42 CDT(-0500)] <Bosmon> I did try to get that debugger working a few years ago and it was a miserable and unrewarding experience

[12:18:45 CDT(-0500)] <Bosmon> But it sounds like it is now working?

[12:18:51 CDT(-0500)] <colinclark> all I want is a text editor

[12:19:08 CDT(-0500)] <yzen> Bosmon: yes it works well

[12:19:19 CDT(-0500)] <jhernandez> oh my god! Bosmon uses eclipse? (I just dropped a myth!) (tongue)

[12:19:20 CDT(-0500)] <Bosmon> colinclark - still the ability to "scope a search within a project" is the one remanent feature from Eclipse I find useful for non-Java programming

[12:19:31 CDT(-0500)] <jhernandez> colinclark: +1

[12:19:35 CDT(-0500)] <Bosmon> It's not clear how I would do that with a simple text editor : P

[12:19:47 CDT(-0500)] <colinclark> I am a pretty inept programmer

[12:19:54 CDT(-0500)] <colinclark> so I prefer my tools to reflect that

[12:19:54 CDT(-0500)] <Bosmon> But my main question is, does the node Eclipse debugger still suffer from the 10 stack-frame limit that we have in node-inspector?

[12:19:57 CDT(-0500)] <yzen> Bosmon: you can with sublime

[12:20:08 CDT(-0500)] <yzen> Bosmon: of course (smile)

[12:20:23 CDT(-0500)] <yzen> who needs more than 10?

[12:20:35 CDT(-0500)] <jhernandez> yzen: that's true!

[12:20:36 CDT(-0500)] <jhernandez> xDDD

[12:20:58 CDT(-0500)] <Bosmon> yzen - anyone who debugs into the framework, I guess

[12:21:06 CDT(-0500)] <Bosmon> I imagine you don't find yourself doing that very much (smile)

[12:21:14 CDT(-0500)] <colinclark> It's like the Node.js version of jessm's adage, "there are always three things"

[12:21:18 CDT(-0500)] <yzen> (smile) i guess where the problem is

[12:21:24 CDT(-0500)] <colinclark> except it's "there are always 10 stack frames"

[12:22:16 CDT(-0500)] <colinclark> yzen: To that I say, "show me your pull request" (wink)

[12:23:53 CDT(-0500)] <colinclark> jhernandez: PUPPY REPORT?

[12:24:06 CDT(-0500)] <jhernandez> heh

[12:24:17 CDT(-0500)] <jhernandez> they're fine

[12:24:27 CDT(-0500)] <jhernandez> and I already have owners for all of them

[12:24:45 CDT(-0500)] <jhernandez> :]

[12:25:02 CDT(-0500)] <jhernandez> http://www.milanuncios.com/cruces-de-perros/se-regalan-cachorros-106566089.htm

[12:25:05 CDT(-0500)] <jhernandez> (tongue)

[12:32:20 CDT(-0500)] <colinclark> wow wow!

[12:32:33 CDT(-0500)] <colinclark> avtar's missing out on this

[12:33:03 CDT(-0500)] <michelled> so cute!!!

[12:33:15 CDT(-0500)] <danaayotte> repost please

[12:33:40 CDT(-0500)] <colinclark> thank goodness for logged channels

[12:33:53 CDT(-0500)] <colinclark> danaayotte: http://wiki.fluidproject.org/display/fluid/fluid-work+IRC+Logs-2013-10-03

[12:34:00 CDT(-0500)] <colinclark> near the bottom there

[12:35:15 CDT(-0500)] <danaayotte> colinclark: thx!

[12:36:08 CDT(-0500)] <colinclark> So we've determined that Eclipse is cool again

[12:36:24 CDT(-0500)] <colinclark> which means IBM WebSphere for Node.js must be the next big wave of awesomeness

[12:36:53 CDT(-0500)] <colinclark> Watch out Kettle! Here comes Local, Home, and Remote interfaces for all your JSON!

[12:46:51 CDT(-0500)] <colinclark> Bosmon: Quick question for you, if you have a second

[12:47:21 CDT(-0500)] <Bosmon> Hi colinclark

[12:47:57 CDT(-0500)] <colinclark> So I'm just about to push your isPlainObject() pull request

[12:48:22 CDT(-0500)] <colinclark> I just wanted to get clarity on what the role of isPrimitive() is in the framework now

[12:49:25 CDT(-0500)] <colinclark> I've removed my monkey patches from Flocking and all is looking good

[12:50:35 CDT(-0500)] <Bosmon> colinclark - hi

[12:50:42 CDT(-0500)] <colinclark> lol

[12:50:45 CDT(-0500)] <colinclark> hi

[12:50:58 CDT(-0500)] <Bosmon> I guess you could say "isPrimitive" is a proxy for the concept of "a kind of object that the framework shouldn't seek to touch"

[12:51:05 CDT(-0500)] <Bosmon> These objects will just be ferried around by object reference

[12:51:17 CDT(-0500)] <Bosmon> And the framework will not seek to copy them, modify their properties, or look inside them

[12:51:59 CDT(-0500)] <colinclark> ok

[12:52:05 CDT(-0500)] <colinclark> whereas a plain object?

[12:52:19 CDT(-0500)] <Bosmon> A "plain" object is what you could call "JSON-equivalent"

[12:52:31 CDT(-0500)] <Bosmon> And entirely equivalent to a decomposition in terms of its properties

[12:53:15 CDT(-0500)] <colinclark> I don't think I fully understand

[12:55:21 CDT(-0500)] <Bosmon> The quality of our detection could be better

[12:55:32 CDT(-0500)] <Bosmon> As jQuery's equivalent of this method shows, the issue is quite complex

[12:55:51 CDT(-0500)] <Bosmon> Since in between the "exotic" objects and the "plain" objects, there is the category of "objects with prototype or constructor"

[12:56:01 CDT(-0500)] <Bosmon> Which for various reasons on IE are extremely expensive to detect

[12:56:55 CDT(-0500)] <Bosmon> Right now we make the facile but not completely accurate determination that a "non-exotic object" is a "plain object"

[12:57:04 CDT(-0500)] <Bosmon> Is that any clearer?

[12:59:22 CDT(-0500)] <Bosmon> colinclark ^

[12:59:35 CDT(-0500)] <colinclark> sorry, one sec

[12:59:40 CDT(-0500)] <colinclark> boss is on the phone

[13:28:48 CDT(-0500)] <colinclark> Bosmon: Ok. So a typed array is not a primitive object, but neither is it a plan object.

[13:29:06 CDT(-0500)] <colinclark> So what does that mean for the fate of said object within the merging system?

[13:30:06 CDT(-0500)] <Bosmon> colinclark - it is treated as if it is a primitive object, in fact

[13:30:27 CDT(-0500)] <Bosmon> At least, all of the current tests sites separately combine the predicates "isPrimitive" and "!isPlainObject"

[13:30:38 CDT(-0500)] <Bosmon> But the tests are broken out in case they end up being separately useful at some point

[14:05:54 CDT(-0500)] <colinclark> michelled, anastasiac: Here's my list: https://gist.github.com/colinbdclark/6815237

[14:06:11 CDT(-0500)] <colinclark> our list, rather (smile)

[16:06:59 CDT(-0500)] <Bosmon> Hi colinclark

[16:07:07 CDT(-0500)] <colinclark> oh Bosmon

[16:07:08 CDT(-0500)] <Bosmon> Did I manage to resolve your queries on isPlainObject?

[16:07:08 CDT(-0500)] <colinclark> hello

[16:07:24 CDT(-0500)] <colinclark> Yes, you certainly did

[16:07:43 CDT(-0500)] <Bosmon> cool

[16:08:00 CDT(-0500)] <colinclark> thank you

[16:08:07 CDT(-0500)] <colinclark> I'll push the code this evening

[16:08:09 CDT(-0500)] <Bosmon> yzen - did you check that your FLUID-5169 is not a duplicate of FLUID-5155 ?

[16:58:06 CDT(-0500)] <Bosmon> Thanks for the report and test case for FLUID-5169, yzen

[16:58:16 CDT(-0500)] <Bosmon> I've updated my FLUID-5155 to include test case and fix

[17:07:10 CDT(-0500)] <yzen> Bosmon: awesome

[17:07:12 CDT(-0500)] <yzen> (smile)