anotherangrydev

WSDL/SOAP are not REST

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.

2006? Come ON!

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.

REST was either popularized or outright invented by Ruby?

What the f* are you on? Or were you born a few years ago and just worked with Ruby since then?

Really, how could somebody be so oblivious to this field in order to state stuff like that?

Tell her that two wrongs never make a right.

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.

Good, thanks.

Do you override 'require('fs')' or do you do some magic at the OS level ?

I was impressed by the Time Travel.

If I delete a file through there, and "go back in time" would the files would still be there?

Don't be so naive. Do you think you can just walk up to Mozilla and tell them: "Sup guys, just bundle this crap into your browser. Please."?

It is not valid. I found it amusing that it even went through.

And its pretty much the same thing now.

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.

Why? Because Apple wants everything done "The Apple Way®©™" and other people just don't care so they just create a substandard implementation and call it a day. And it's only going to get worse now that they want to push Metal everywhere.

How many different HR departments?

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.

Edit: And this is wrong because... ?

What a time to be alive. Telling someone to mind her own business is considered rude.

Ok, let's play pedantic DannyBee.

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.

Best luck.

I agree with you. Things need to be solved with a different structure.

You're the 1%, then.

Honestly, I haven't met one decent guy in HR in a loooong time. Quite the contrary, I have plenty of bad experiences with HR that made me believe those things. I'll give you my favorite examples:

I once got fired because I told some bitch (she was really a bitch, and that's not just my opinion, the whole workplace thought of that) to mind her own business. I was on a break and reading a magazine when she came in and started lecturing me on to "why I'm not doing other stuff? why do I read those kinds of magazines? (It was a gossip magazine, but who cares it was what it was nearby) I'm a little old for that." Politely but firmly told her something like "This is my break. Fuck off, you can't tell me what to do on my break and I read whatever I want to". She left. Three months later got called to get fired, turns out she was secretly raising reports about me that were small stuff (and completely fake) like "... was asked to do X and refused", "... yelled at a client", "... reads magazines while at work (of course)". When I had like 10 or so of them she fired me because of a "bad overall attitude" and those were her (fake) proofs. That's the kind of shit HR LOVES to do man.

Another one. I once knew (but not as in "a friend told me", I saw it) of a place where all the candidates that got hired were because they were laying down with the girl that ran the interviews. Later when they got the job, they started to get fired when that girl found them not sexually appealing anymore. Yup.

I think there has to be something psychological behind that, because other while other teammates may be assholes your job does not depend direclty on them or you are pretty much at the same level. Since HR is above you and can fire you at will there is a lot of power bestowed to only one side of the parts involved. I think it may be some kind of Stanford Prison stuff right there. Sorry to call it mate but your field is a rotten one.

HR is never your friend. Aside from the job they're required to do, HR usually attracts people with despicable morals and class. They wont hesitate on lying to you, set you up on to something, threaten you, whatever it takes to get what they (personally) want. Stay clear of HR, that is true for 99% of jobs.

Ok, try testing with packets of around 128-1024 bytes.

A 'good' result for an i5-i7 core is to get at least 10k requests per second on that situation.

You are gonna live or die by this measure dude, so work on improving it. You are around 100x far from it but if you're lucky you can get there with 'just' two 10x improvements. I suggest you to look into Flame Graphs [1], they are awesome. I have used them to pinpoint exactly where are the 10-100x bottlenecks on my code and unclog them.

Also, about your website, just make it sound less like an infomercial and you'll be fine.

And last but not least, best of luck!

[1] http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html

Thanks for your reply. Pretty good project you have there, and your overall mission, well, it looks like a moonshot but it's noble and pure. I like that.

Have you measured how many requests per second (reads/writes) can you get at max? (For some given hardware configuration)

If you're the author, can you give specifics on performance?

Ok, to clarify, yes they were authentic amazon emails.

Not only that, they had a ticket open, this was somehow a 'case' and I had a support ID and everything.

Awww, come on...

Edit: Just checked them, I have them right here, most of them are from payments-verification@amazon.com, they wanted ID to verify the card details or something like that. Which I found it really weird because the account has been running for years and card's haven't expired or been changed.

I agree with you but there's no "quick email or phone call" with Amazon, and that's an issue for many people.

I want to share an experience that I had a few months ago, to see if anyone had something similar.

I have an AWS account that I use to upload stuff to Glacier and leave it there. My monthly fee comes to about $0.20/mo and that's been going since around 5 years (previously it was just on S3). The data I store there is not encrypted (not that they would be looking at it, right?), nor is anything sensitive/illegal at all. Aside from that, I ocasionally spin a cheap EC2 instance to test some new binary before installing it or things like that.

Anyway, around March I received three emails (they were spaced like 6 hours or so apart so I've read them all at once) and the subject was something like "Important Notice regarding your AWS Account, Urgent! Open Now!". The first thing I thought was sh*t, my account was hacked and now I owe a million dollars to AWS.

To my relief that wasn't the case, but they wanted me to send them many documents that I consider personal and for no reason at all. I replied something like "Is something wrong?" and they said it was standard procedure, which is weird because I've never knew of anything like that. Things eventually went to "send us a scan of your passport or we will terminate your account", passport because that's the only ID I told them I had. I eventually told them to piss off, I figured that $0.20/mo and the things I had there are not worth the worry of sending that data to someone hiding behind an email. They didn't reply anything and then... nothing happened. It's been half a year since and everything is business as usual.

It was weird, and I never could make sense of what they really wanted, but anyway, just thought of sharing that when I read this guy's experience.

You do not have to lean at all to turn, if you don't want to [... but ...] you won't be able to turn as sharply.

You basically proved my point.