Well if you define REST as "Web Apps developed with RoR" then I guess you're right, Rails is definiteley the pioneer of Rails development.
>You've yet to refute that argument
There was (at least) Tomcat deployed and quite popular, and yep, everything moved through REST interfaces. Even with that one and the huge success it had in the enterprise world, I wouldn't dare to say that the success of REST relies on Tomcat anyway.
REST hit it big with the www, www is REST's killer app. Those things are quite literally the first ones you should know when you start developing for the web.
How about the whole WSDL/SOAP services that appeared way before that? You're telling me that Rails was the one who came out with the modern REST ideas?
That's total tech illiteracy right there. Damn, you even had the nerve to defend that feeble argument.
Even if it were a database of known murderers (or sex offenders , or whatever crime you consider to be the worst), it is still private information. So it's a shame that those 'hackers' got away with it.
Try WebGL on any Mac (Safari is the worst performer of them all btw). You will see a bit of lag, frame drops, CPUs at 100%, a lot heat and your battery will die in two hours max.
Open the same site on a Chrome/Windows machine (with comparable specs of course) and you don't see any of that trouble.
The runtime is pretty awesome as well. I remember the work of people like Joa Ebert exploiting the platform and the language to the max, really cool stuff. The world is barely coming closer to what Flash was capable to do... 8 years ago.
IMO Apple killed Flash not because of the "battery, security, etc..." "issues", but because they didn't want their devices to depend so heavily on another company. It was business, and strangely, Adobe didn't even put on a fight. And they just spread FUD and all the developers that didn't know better went with it, but I agree with you, shitty flash developers will now just be shitty HTML developers and everything will be the same in another 5-6 years or so.
Ok, thanks. Haven't read the spec, that's why I was asking.
>However, the general consensus is that promises should be part of the microtask queue, and for good reason.
That's the only bit I found in the post regarding that. Didn't sound like 'it's in the spec' to me.
Regarding the example, (I'm gonna sound like the SO posters that I hate but) there are other appropiate places where you should hook up that callback. If the one you chose does not play well with Promises yet (because you want to access an object thats at the end of its lifetime and not guaranteed to exist), then ¯\_(ツ)_/¯.
I asked for an example where the program breaks because I thought that if you queue up things 'for later dispatch' you shouldn't be worriyng about the order where they dispatch. If you're actually worried, then chain them together with the classic callback stuff.
But, I'm not demeaning your post (I see you're the author), it was really good. The main issue is see is (as you stated in your comment) that Promises as microtasks would increase their performance. It is a shame, however, that we as developers are not able to queue microtasks directly (like when using setImmediate, process.nextTick) :(
Always had bad experiences with HR, with around 6-7 different companies. Talking with colleagues on the same industry and others found out that my experiences are not isolated incidents, but quite the opposite they've observed pretty similar things. And finally, have a few friends that work themselves into HR and outsourcing (for SAP & Oracle) so I can speak for that environment pretty well, it is a rotten field. And yeah I'm extrapolating from that.
I can tell you something, I probably talked about this subject at least 100 times during my "professional life" with many different people, I have yet to hear a good experience from someone regarding their HR department.
Mind sharing yourself which bucket do you fall into?
Does the spec explicitly tells about how to time tasks vs microtasks? I was under the impression that it was up to the implementation and not relevant.
To add something more, I would really like to see an example where this actually ruins a program execution.
>I don't think you have anywhere near the kind of data to generalize an entire profession across all industries :)
>The vast majority of people i've met who feel like you do are people who were, IMHO fired pretty fairly, but are ashamed to admit that maybe they weren't performing as well as they think, so they blame the system.
We're gonna need a source for that too! Or wait, were you discrediting one opinion with another one?
>"Stay clear of HR, that is true for 99% of jobs."
>Having met at least 50+ people in HR who aren't what like you say, i'm going to call complete bullshit on this.
Ever knew of what the '%' sign means? I can get you 50+ people that are in jail and that were later proved to be innocent. Does that mean we should set all of them free?
Waiting for your downvote or a reasonable argument :^)
Rich, you know what dignity is? Dignity is being the same person disregarding the situation where you're currently involved.
I see you standing here as a person who is always polite and correct, with a perfect vocabulary and behavior for even the most adverse situations in life. I really, really hope your life crosses path with a woman like that one and you end up in a situation like mine. I would like to see you handle the same situation with the morals you claim to have. Until that moment you will know, for yourself, if you really are the person you claim to be on real life or if the intention behind your comment was just to impress a bunch of people in an anonymous forum.
Well if you define REST as "Web Apps developed with RoR" then I guess you're right, Rails is definiteley the pioneer of Rails development.
>You've yet to refute that argument
There was (at least) Tomcat deployed and quite popular, and yep, everything moved through REST interfaces. Even with that one and the huge success it had in the enterprise world, I wouldn't dare to say that the success of REST relies on Tomcat anyway.
REST hit it big with the www, www is REST's killer app. Those things are quite literally the first ones you should know when you start developing for the web.