Elvis: Renlo: both, although we write our own webview wrappers

Elvis: Often they just run directly in mobile browsers too

Traher: Sawbones: no pay no work

Elvis: And its somewhat fun, but i’m probably leaving soon to return to native development. lately we’ve started focussing on quantity over quality, and I haven’t enjoyed it much since then.

Zubke: Quantity of what? bugs introduced into code? :

Elvis: Ha, more like hours worked

Baumgardt: Torkable: I’m currently in an office filled with people who work the weekend for no overtime pay

Elvis: Sawbones: its pretty common for programmers not to be paid overtime

Mcjunkins: Last-child selector w/ conditional statements problem, please help: http://jsbin.com/paxotapixe/1/edit?html,js,console,output

Elvis: I’ve only ever been paid overtime when it was for hourly positions.

Strimling: Thanks for reminding me not to move to the us

Schramek: Sawbones: Overtime w/o pay can be common, but you much be salary. Also, if they expect that often the pay should reflect. If not find another job

Meche: I’m so scared to look for another job and just see the same thing

Caire: Americans allow themselves to be slaves it’s ridiculous

Muffoletto: Chokidar reports files that aren’t even there to be added

Schramek: There are plenty that treat you nicely. You can ask in an interview what the typical work week looks like

Morrell: Hello, I have a question: I want to request some data out of the db. I try It with Ajax but I don’t get a answer in the console.log. Here the code: https://gist.github.com/anonymous/baf9a60c24b98cb85032

Burde: Schramek: It ****s because I was lied to about the work culture here in the interview

Elvis: If you don’t like it you should leave. my understanding is that expecting overtime is not super common for web development.

Vuoso: Any idea why the login function wouldn’t be reached? https://gist.github.com/vioz/ef5aec70c48f2eeec705

Faines: Does anyone know if the Promise object gets garbage collected once they been fullfilled?

Kalinoski: Pikul there is no way to forcibly trigger garbage collection afaik

Lory: But when it happens will it release old promises?

Kalinoski: If they’re no longer in scope

Kos: For example, var p = Promise.resolve; p = p.then.;

Lorch: P is no longer the old promise

Kalbfleisch: Pikul, promises are objects and follow gc rules for objects

Kalinoski: The original promise will get garbage collected

Bond: Pikul, old promise goes out of memory then

Kalinoski: As long as there are no other references

Mantik: What if old p were also holding a reference to the new p

Kabala: Pikul, Kalinoski, actually no

Chantha: Old promise must be still reachable if it’s not yet resolved

Fragozo: Calling .then does not resolve it

Kalinoski: The async scheduler still holds a reference to it

Kalinoski: For whatever implementation

Davern: Pikul, do you have memory issues from piling up unresolved promises?

Glazier: No, i’m just wondering if it’d be safer for async loops to use callbacks

Elvis: Callbacks will use less memory but not significantly less.

Rowzee: Pikul, for performance-critical code

Elvis: And will basically have all the same reachability issues.

Morillo: Creating less gc stress is always good

Babu: I am ok with a small bump on memory for promises, but not if it’s going to keep using more and more every as time goes by

Elvis: No more than callbacks would

Elvis: Unless you are using them wrong.

Borgelt: I use lots of promises in web apps and my process memory usage is constant at 120-150MB