Starratt: Technically the second one is fewer characters, and potentially less typing.
Jesperson: It looks cleaner but might not be as readable
Elvis: I always put them on separate lines
Elvis: At least nearly always
Fletchen: Samssh: well I’d insert a tab where ‘var’ would’ve been, so I guess it takes up the same amount of space
Cobler: Keep the newlines in there for readability.
Elvis: Oh, i prefer it having var if its on its own line
Elvis: Since if i need to get rid of the variable it’s easier
Elvis: I think the first is def. better.
Elvis: Also adding another is easier, i don’t have to think about ‘okay this is now at the end’ or something
Kalkman: Yeah being able to quickly re-order and drop elements is nice
Myatt: The first one has the advantage of not breaking things if one of your middle vars needs a complex definition.
Elvis: I don’t see any advantages to the 2nd either.
Chowanec: The 2nd one looks neater when you have a bunch of fairly short definitions
Bogatay: But I think I’ll stick with the former
Elvis: Occ***ionally i’ll put two variables on the same line, but it’s pretty rare. usually it’s when i have a bunch of x, y properties to define and i want to make the symetry obvious
Elvis: And i odn’t think it will have to change any time soon
Elvis: Although looking, i guess the one place i thought i did that i didn’t.
Keithley: The only advantage to the second group in my opinion is that is looks cleaner for large groups of variables. But really, if you have that many vars you probably need to do some refactoring.
Hlavaty: Samssh: lol my dependency list mostly
Elvis: Samssh: not sure i agree that you need to do refactoring necessarially. numerical code you often end up with a lot of intermediate variables just to avoid having super complex/dense expressions.
Exner: I made a bunch of comments on a pull request the other day because of method #2 — thought they were accidental globals.
Gurecki: Tcsc, Hence ‘probably’.
Laginess: There are always exceptions.
Luffman: I have a large JSON object with PDF strings and their coordinates in the PDF, and I have a ‘profile’ that maps these coordinates to their meaning. I’m wondering if it’s more efficient to go through every string from the PDF and check the profile for each one, or vice versa; read the profile and find the string in the PDF JSON
Elvis: I always use semicolons.
Mcmurray: I imagine searching through the PDF for each profile value might be more work than scanning the entire PDF once while matching it to the profile
Stach: Yeah i’d make a cache / use the profiles.
Shahim: So find the related string in the PDF for each profile item?
Chancellor: Tbf it would be easier to code
Elvis: Baxx: i just looked at that physics code again and you know where it handles the collision with walls? and does this.y = world.height-this.r-1? and this.x = world.width-this.r-1? the – 1 is a bug. if you get rid of it, the simulation is much more stable.
Braff: But probably more resource intensive
Kuehnhold: Anyone use sublime text?
Oyabu: I’ve used it for a day
Defusco: Tcsc: cool just removed it – I’m just looking at it with like 2 entities at the mo trying to see how the collisions works
Pizzo: Zumba_ad_ search for files or in files?
Surridge: I found it but not sure if it’s good ankr, http://sublime-text-unofficial-do***entation.readthedocs.org/en/latest/file_management/file_management.html
Harlin: Zumba_ad_ that’s what I use. Just hit Cmd+T and start writing the name of the file.