Leandro: In related news, Node4.0 should release next week using v8 4.5 😀
Leandro: Amazing how effect the iojs fork was
Fowles: From 0.12 to 4.0. It’s amazing how versioning works 😀
Sambrook: Hameen: like the cl***path hell in java?
Blackstock: Sambrook: that’s one of its many problems, yes.
Lunch: Well the amazing part is joyent moving out
Sambrook: And the rest is apache commons in all it’s versions all incompatible to the next and used by many libraries just because :
Tadena: Anyone know wp dev that can PM me?
Hulsizer: Though cl***paths *could* have been great if they did it right :/ Purr and Newspeak use a very similar mechanism.
Sambrook: Hameen: still, if you have two libraries that have a package.json depending on different versions of the same npm package. what’s going to happen?
Sambrook: That would be similar to java cl***path hell
Yant: Let’s just use nix for everything
Huch: Sambrook: no. At that point your program may work, or it may not work
Mcgrann: Django_: try #wordpress they are helpful if not annoying
Leandro: I just wish package.json would let us have trailing commas, I swear I break that every time I touch the file
Shazier: Fooey: it’s not supposed to be edited by hand
Pillado: Hello, I am using a XMLHttpRequest to send the URL of the current page to a ASP.NET script. when I just send the Url using “xmlhttp.send’url=’ + window.location.href + ‘&data=hello'” the ASPX page thinks that the get parameters of the URL are ment for it. so, if the current page is http://example.com/hello.html?name=Blah&code=blahblah the ASPX gets: url=http://example.com/hello.html?na
Lindstedt: Me=Blah&code=blahblah&data=hello Problem is that now ASPX thinks that name=Blah&code=blahblah are parameters ment for it. How do I fix this?
Leandro: Babel and eslint let you load up their config in package.json now
Yant: Fooey: yeah. a friend observed that a json p****r can accept all valid json while completely ignoring commas
Yant: Commas in json are technically unnecessary :
Leandro: I haven’t decided if loading up everything in package.json is better than sticking with .babelrc and .eslintrc
Senethavilouk: Dash: colons aren’t necessary either. It could very well be closer to EDN
Cone: MDTech-us_MAN, that’s not how you specify the url for the XHR object
Sambrook: Dash: Isn’t it a syntax error when you do not use a comma to separate pairs in a hash?
Yant: Sambrook: yes, but the grammar could be changed to not have commas and nothing would be lost
Yant: Well OK, you’d need spaces instead of commas in some places
Badanguio: Cone, I want to send the URL AS A PARAMETER
Yant: Wait, no, you would not.
Yant: Object keys have to be strings.
Sambrook: Dash: I generally do not use ; before n but sometimes I get really strange errors, especially around function declarations. I’d imagine without commas you’d run into similar things, maybe even stranger
Cone: MDTech-us_MAN, use encodeURI
Forsman: Js will be around some more years within web ecosystem?
Yant: Sambrook: in js yes. not in json :
Brostoff: So, xmlhttp.send’url=’ + encodeURIwindow.location.href + ‘&data=hello’
Yant: Of course the original appeal of json was that it’s evalable js source, but that doesn’t matter today
Cone: EncodeURIwindow.location.href + ‘&data=hello’;
Sambrook: MEGAGHZ: js will be replaced by scheme in 2016
Riculfy: Dash: you’d need spaces in 1,2,3