Worse, the H1Bs require their employer to sponsor them to remain in the United States, which they will only do if the individual is working for them.

As a result, the employer not only holds and H1B's livelihood under a Damocles Sword, but even their residence in this country. You want to quit? Well, I hope you're prepared to move yourself back to where you came from on your own dime, which is also what happens if we fire you.

So, the employer has even more power over H1B workers, to the point where the worker is unlikely to report anything but the worst abuse...

It even syncs the disks before shutting down! v_v

Such a non-news story... omg, this this is "interesting" in so far as an odd tool that has little possible use(?)

That's my thinking...

Congresscritter?

I for one welcome our new -hole gender-neutral name style for jobs that are essentially "lie about this in the least possible lie, so that it still puts us in a good light"

In Germany, autopay comes with an authorization limit... basically, "if the bill is over X,€ don't autopay"

I'd prefer to see this on the autopay here in the states as well... because I'm fine with authorizing autopay for any bill less than $60... but if it reaches into the thousands, or even the hundreds, then I damn well don't want to authorize the autopay!

10 separate streams at only 29 Mbps... that means you could do ... 2^2... but it's 8k, so 4^2 = 16... 29/10*16... 46.4 ... so, you could still do 8k Netflix on 50Mbps...

You know, I always hate how my grunt work for companies makes them 4 times the money they pay you. It's just greedy theft. We should start a movement where the means of production are owned by the workers rather than investors and management!

What does the Skilled Occupation List have to do with this?

First of all, I would make it so you can press the Enter key and it conducts your search. Forcing people to either tab or navigate their mouse to the button makes it a little annoying.

And inside, a modern x86 processor is actually a giant hardware emulation of x86 instructions with a RISC/VLIW core... You call it cheating, and I call it optimizing.

But this would happen with a macrokernel as well... you can't just magically make networking overhead disappear...

I wasn't intending on saying that CISC was superior to RISC... what I was more saying is that there has been more money put into CISC processors, and so they develop faster.

It's just a simple fact of money == better access to stuff to make more money.

This was basically what I was trying to say. More capital investment typically means better outcomes.

But hardly anyone is running the stock Android anyways. They've all expended on the code, and made it different. Almost no one actually uses the "official Google version" at all...

But they can't because it's open source software. No one could make all of the Linux Distros use the same official kernel... it's not possible, because it's open source, and you can make it yourself.

But this is already the case. Amazon and Barnes and Noble do not sell Android devices with Google services on them.

I don't get why people have such a difficult time understanding that Google can't wrangle these cats, because it doesn't have an Iron Fist on the source code...

I've never seen a RISC processor that can match the performance of the best CISC processors. You know, nevermind the fact that tons of money has been poured into CISC processors making them faster and faster.

Sometimes, it's just a matter of where the attention has been placed.