Marallo: But i think. they are just f*cking retards, LOL
Callan: Choki_: it’s decent i guess
Higy: Anyways, I should ask here instead maybe I won’t get downvoted, LOL
Custodio: It’s really simple, i just can’t decide why to use that value. Maybe there are factors why not to do that
Rogillio: Zumba_ad_: please don’t use that word. And, really, this isn’t a channel to come and bash people.
Shelsy: Choki_: Eloquent is a decent introductory book.
Clerkley: Eloquent is a decent introduction to programming
Sission: So here is my question, why would we want to cancel an ajax call on the 10th second if we haven’t received the response yet from the server?
Cifaldi: But I don;t think JS is good beginner language
Willhite: From what I know, the timeout period will be ignored if we get the response within 10 seconds
Vallone: Zumba_ad_: your question got downvoted because its not a good question
Verrett: To “multiply” a string, is it considered hacky to do Arraynum.join”string”?
Quates: Higuchi: it’s ok, they just want to feel like god 😀 It makes them feel they are so good
Cormican: The behavior of an object where a property has a getter but not a setter is a bit bizarre. When I set it, no error, but nothing is set. Silent failure.
Velie: Is the expected behavior defined anywhere?
Frantzich: I’ve had bad luck with stack overflow as well. idk if i think there’s a good answer to your question, but i feel like i get no response or worse, ‘you shouldn’t need to do that’ out of most of the questions i ask. so i just stopped bothering with it.
Krist: Zumba_ad_: what do you mean by “cancel”?
Kruegel: Profsimm: the behaviour of getters and setters is weird all over. Not just in that case.
Lungsford: When we set timeout property in jquery ajax like 10 seconds, jquery will cancel it if it doesn’t receive the response from the server within that time period
Streva: Profsimm: they were pretty much an after thought, that was first only introduced in SpiderMonkey. No one cared about how they would interact with the rest of the language, so they’re, uh, awkward
Worchester: It will show as failed in chrome’s network tab
Stien: Or sometimes canceled
Pessoa: I couldn’t remember which one
Vitello: I’d like an authoritative note if someone knows, how is a get without set supposed to behave.
Firebaugh: Anyways, if I set timeout to 60 seconds, and api responds at the 50th seconds, i’ll get the data and be able to render it
Pfleider: However Dekok, I wasn’t sure if it’s better to set a lower timeout and inform user that the call got canceled rather than the user waiting for the spinner to keep on running
Revette: Zumba_ad_: right, you have timeouts because you don’t want to be waiting forever for a response. At some point, you have to consider something a failure, and you can’t know what caused that failure in a network maybe the server is too busy, maybe your network is bad, maybe the network is down, maybe ., so the best you can do is define a certain amount
Dieckman: Of time past which you give up and decide to try something else
Cargo: How much time to wait for is something YOU have to define, in the context of your application. There isn’t a general answer to that
Linke: Exactly so in the real world, I’m not really sure of a good value to use. is 10 seconds good?
Timmreck: I think i usually use 20
Stelb: But its always totally off the top of my head
Mallas: Profsimm: The behavior changes depending if you’re in strict mode or not.
Koles: And i usually try multiple times also
Vankeuren: I think i’ll remove our 60 seconds and use a lower value. This way, we’ll be able to check our logs and ****yze why it’s taking so long. We’ll be able to inform the server and api folks
Jurgenson: Profsimm: And you should always be using strict mode for your own code