Dash: sure, you can have.

Bogacki: It works on codepenio though: http://codepen.io/dimsemenov/pen/vKrqs

Caryl: The content of the inline popup is already visible when opening the page

Humpert: Http://imgur.com/M5Y8F2U

Trucchi: Higuchi: you’re not wrong that it could easily be confusing if overused of course ;-

Trucchi: But doing intricate partial applications is never gonna be great.

Sowders: Is there an event for the tab is about to lose focus?

Ballmann: What can i replace “options.timestamp” to get current UTC time and not my current system time?

Markstrom: Https://facebook.github.io/react/blog/2015/09/10/react-v0.14-rc1.html

Rundlett: The best thing about database questions is that they always seem like good questions. Even if they are the equivalent of “can a variable store a value” in JS

Lescavage: I have this case where the Number wrapper object does not === a reference to Number. anyone know how the ref to Number could change?

Fouse: Var x= { y: Number}; function doSmthing{ return Number !== x.y };

Torain: DoSmthing returns true

Riska: Is it a floating point value?

Alliston: Jesse123: do you have a real example that reproduces the problem you’re seeing?

Hallgren: You have a number wrapper?

Pane: Because, uh, there’s your problem. never use those.

Boddie: New Number3.4 === 3.4

Glovinsky: New Number3.4 === new Number3.4

Meringolo: Theres pretty much never a reason to use them.

Gruell: What’s happening behind the scenes to cause that issue tcsc ?

Kampman: As a rule of thumb, wrapping objects is always a bad idea. Sadly a lot of OO languages seem to encourage you to do this, even though it’s bad.

Bacone: Kamuela_iOS: objects are compared by identity

Solymani: And javascript world slow down, you’re moving too fast. We should have a programming labor day where you stop pushing code!

Jeffress: Dekok: what’s bad about wrapping objects

Tricoli: Dekok: so is Number3.4 forever an object?

Jeffress: Lewis: labor day is the one where you work hardest though

Mehan: Dash: the types change

Hepp: Lewis: its long overdue 😛

Jeffress: Dekok: only if your type system is insufficient :

Farnan: The semantics also might change. It isn’t interoperable anymore. And depending on how things were designed, you now have very hard problems to solve because of Getchell.

Floan: Kamuela_iOS: no. only if you use new

Cluckey: Of how Getchell makes it hard to extend/refine things*

Jeffress: Sounds like FUD to me, what’s the difference between “wrap” and “extend”

Nurthen: Wrap you dont add any new functionality, exted you do.

Atwell: Dash: any nominal type system is going to yield different types. Structural type systems might cope better with that.

Arhelger: So does that mean Number returns a primitive? If so, why is it compared as an object?

Jeffress: Dekok: meh, you just have to have a coercion protocol in your type system

Alexandropoul: Kamuela_iOS: Number is a primitive, new Number is an object

Jeffress: So that some function or whatever that wants an int can ask an object “plz give me the int you wrap, if any”

Marotte: So why does Number1 !== 1?

Mccallum: Anyone used datatables here and can tell me if its possible to shorten the length of a displayed column field? with like an elipsis, and when the user clicks the field it will display the whole thing?

Chaudet: Oh I’m sorry I totally missed the use of new in all of this conversation

Clegg: I want to show like. 25 columns in a table but I want it all to fit nicely

Swearinger: Dash: sure, you can have things that convert things to other things.