I think you are misattributing his snark. In his regular column he has a recurring section called "Blockchain blockchain blockchain" such as in [1] in which he covers how the finance industry itself is trying to apply blockchains to everything. It's the new fad, they are in the Peak of Inflated Expectations [2]. So while it might be true that some bankers are afraid that Bitcoin is going to replace them (I have no opinion on that) the author is highlighting yet another case where blockchain is supposed to easily solve any difficult distributed ledger problem.
Well TBH you do get to pick which Hadoop-related components need to run, HDFS's Datanode itself is happy with just a bit of RAM. I do understand the concern though.
You're probably happy with what you have in prod but if you get some time to try out Kudu feel free to drop by our Slack channel for a chat! http://getkudu.io/community.html
You seem to have a pretty typical use case that we're targeting. One thing to understand about Kudu is that it doesn't run queries, it only stores the data. You can use Impala or Drill, they'll figure out the locality and apply the aggregations properly/push down the filters to Kudu.
Did you initially pick ES over systems like Impala because of the lack real time inserts/updates when used with HDFS?
Analytics is what Kudu was designed for (it's not just marketing), so some tradeoffs were made. You'll get the biggest bang for the buck if your use cases are heavy on inserts and big scans with selective filters. Other use cases will perform ok or meh VS other storage engines. Also note that Kudu is still pre-1.0.
The issue isn't that MongoDB is eventually consistent, it's that the documentation claims that in some cases it's strictly consistent[1] while Kyle found that:
"MongoDB, even at the strongest consistency levels, allows reads to see old values of documents or even values that never should have been written."
Will it be the end of eat24's weekend coupons? When they started they were regularly giving 3-4 bucks per coupon. Now, I can't remember the last time it wasn't $2, apart from those times when they teamed up with other companies like Paypal and gave away $10. I'm actually surprised it went on for so long, seems like an expensive way to help retention.
That along with: "Many of you use Direct Messages to reach the people and brands you’re only connected to on Twitter."
So the blog post's target audience seems to be their own users (you experience/use), but spoken in advertiser-speak. It's a not so subtle reminder that the user is the product.
I wonder why Google translated "huis-clos" to "camera" in the header text. Best I could find is that Sartre's Huis Clos was originally called "in camera" which means: http://en.wiktionary.org/wiki/in_camera.
> I think it's more likely they didn't understand the law fully rather than malicious intent. The workers were after-all, temporary and were not going to be staying in the US permanently.
Oh yeah, we agree there, what I meant is
that of all the times companies brought over employees here to work for some time, this time it so happened that their salary was below the minimum. If they were bringing over people from, say, Canada or Germany, they'd probably be paid way above the minimum.
So my guess is that they are actual EFL, India, employees who are flown in for some time, probably on a tourist visa (I've seen that elsewhere), but still paid their normal salary while they work here.
The truly exceptional situation here is that their salary happens to be so low it's below the minimum salary (edit for clarification: exceptional in that it also happens with employees whose salary is above the minimum, but then article would seem a lot less sensational).
For those interested, a good source for a lot of publicly reported crashes, accidents, incidents and whatnot is The Aviation Herald. Here's the list of all their recorded crashes sorted by occurence date (toggle the icons next to "Filter" to see more kinds of events): http://avherald.com/h?list=&opt=7681
Ah I see where you were coming from, so you're saying that it's ridiculous since most spouses probably gave up/found something else to do, and those who would really benefit from a relaxed rule are those who just got their H1.
The way I see it, in the best case scenario a spouse can now get an EAD in 2 years (1 year before starting the GC process, 1 year to get the PERM and the I-140). Still far from being able to work right away, but progress nevertheless.
I don't think it's ridiculous, and the current 97k H4s that will now be able to work are probably pretty happy about it [1].
Regarding the L2s being able to get their EADs but not the H4s, keep in mind that the latter are not the only ones in this situation, it's the same thing with TN/TD. And then you have the E-3 spouses (Australia) who _can_ get their EADs[2] :)
I think that the problem is that each visa/work status was created separately, so it's more than just a case of "since it works for this one, why doesn't it work for this other one". I agree with you that this current situation is ridiculous but I'm happy that they start addressing those issues, even if piece by piece.
As whitenoise mentions below, it's only if your I-140 has been approved or your H1B has been extended that your spouse can work.
Even if you are getting your H1B this October, and assuming that you could qualify for EB-2 in ROW and that your company starts the green card process the day you start working (more likely it's gonna take 6 months to a year), your wife still won't be able to work for another 2 years. Just getting the PERM these days can easily take a year.
> First, people traveling together tend to sit next to each other, so ordering by "columns" instead of rows breaks them apart in the queue
You can order by column but still let families together, for example with United you can board with your group/family's lowest group number. This means a 1K with boarding group 1 can bring in his wife and kid (who are somewhere between 3 and 5 if they don't have status) on the plane all at the same time. This way you can fill up whole rows at once.
1. https://www.bloomberg.com/view/articles/2017-01-31/mirror-tr...
2. https://upload.wikimedia.org/wikipedia/commons/thumb/9/94/Ga...