Hm. The covenant of Noah is about two paragraphs before this part (King James Version) which is used for various justifications of slavery and discrimination against all sorts of people because they are said to bear the Curse of Ham. If folks wanted to use the Bible to justify anything ISIS says is justified by God's words in the Koran, they could easily do so.
18 And the sons of Noah, that went forth of the ark, were Shem, and Ham, and Japheth: and Ham is the father of Canaan.
19 These are the three sons of Noah: and of them was the whole earth overspread.
20 And Noah began to be an husbandman, and he planted a vineyard:
21 And he drank of the wine, and was drunken; and he was uncovered within his tent.
22 And Ham, the father of Canaan, saw the nakedness of his father, and told his two brethren without.
23 And Shem and Japheth took a garment, and laid it upon both their shoulders, and went backward, and covered the nakedness of their father; and their faces were backward, and they saw not their father's nakedness.
24 And Noah awoke from his wine, and knew what his younger son had done unto him.
25 And he said, Cursed be Canaan; a servant of servants shall he be unto his brethren.
26 And he said, Blessed be the Lord God of Shem; and Canaan shall be his servant.
27 God shall enlarge Japheth, and he shall dwell in the tents of Shem; and Canaan shall be his servant.
Because if it is, you need to pull your head out of your ass and go and do some extremely basic, cursory, research on the situation in the US. There are for sure some loud fundy Christian that like to whine about science, evolution in particular. However they have had little and less success in pushing their agenda and the US remains a powerful center of scientific research.
Trying to equate the US to ISIS is beyond stupid.
The headline says farmers. The text says farm workers. Very much not the same thing. A farmer is the owner of the farm. A farm worker is generally a hired hand, often (though not always) a migrant, and if so typically from Mexico or farther south.
The story suggests that the multi-drug-resistant bacteria are the result of antibiotic treatment of the animals at the farm. This misses another possibility:
In Mexico, most antibiotics are over-the-counter, much like asprin here in the US. People who feel ill or have some infection often buy and take them. Typically they use them until they no longer show symptoms - then stop, rather than taking a full regimin and killing off all the bacteria. (Why take more of the non-free drug once the symptoms are gone? Waste of money, right?) This is a recipe for creating drug-resistant bacteria.
Of course if an infection is resistant to one antibiotic, a paitent is likely to try another, and another, and so on until they find one that works. THAT's a recipe for maintaining and improving the bug's resistance to the front line antibiotics while breeding resistance to others.
As a result, a substantial fraction of the workers arriving from south of the Mexican border are carriers of multi-drug-resistant baceria.
Meanwhile, a farming operation is likely to give a limited number of antibiotics continuously, so non-resistant infections are wiped out before they can develop resistance, and if they do develop resistance it will be to the particular drugs used, rather than the universe of antibiotics.
Of course, infected workers can infect livestock, just as livestock can infect workers. And infected workers can trade infections around, just as livestock can. (More so, since the livestock tends to be kept separated, to reduce both disease spread and breeding by unintended pairings, limitations that farmers can't impose on their workers - and would be unlikely to try even if they could.)
So it seems to me that responsible researchers would go a bit farther before reporting: Like by doing genetic testing on the strains of bug in the various workers and the livestock, and running models on the results to try to identfy whether the bugs are from the herd or the workers.
I don't see any such work alluded to in this popularized reporting. It seems to just assume that the bugs were developed on the farm and spread to the workers. I hope this is a disconnect between the actual research and the report, rather than an accurate characterization of the research.
How is the objective-c compiled and ran on Dalvik? Are you doing: objective-c -> LLVM -> dalvik bytecode?
It isn't. It runs natively via the NDK.
I maintain the GNUstep / Clang Objective-C stack. Most people who use it now do so in Android applications. A lot of popular apps have a core in Objective-C with the Foundation framework (sometimes they use GNUstep's on Android, more often they'll use one of the proprietary versions that includes code from libFoundation, GNUstep and Cocotron, but they almost all use clang and the GNUstep Objective-C runtime). Amusingly, there are actually more devices deployed with my Objective-C stack than Apple's. The advantage for developers is that their core logic is portable everywhere, but the GUIs can be in Objective-C with UIKit on iOS or Java on Android (or, commonly for games, GLES with a little tiny bit of platform-specific setup code). I suspect that one of the big reasons why the app situation on Windows Phone sucks is that you can't do this with a Windows port.
It would be great for these people to have an open source Swift that integrated cleanly with open source Objective-C stacks. Let's not forget that that's exactly what Swift is: a higher-level language designed for dealing with Objective-C libraries (not specifically Apple libraries).
Objective-C is a good language for mid-1990s development. Swift looks like a nice language for early 2000s development. Hopefully someone will come up with a good language for late 2010s development soon...
It wasn't just about interface. People tend to forget how search engines did an absolutely horrible job of intelligently ranking the sites you wanted to see.
I find it pretty easy to remember - I go to Google today.
The UI was what made me switch both to Google originally and from it some years later. When I started using Google - and when Google started gaining significant market share - most users were on 56Kb/s or slower modem connections. AltaVista was the market leader and they'd put so much crap in their front page that it took 30 seconds to load (and then another 20 or so to show the results). Google loaded in 2-3 seconds. The AltaVista search results had to be a lot better to be faster. I switched away when they made the up and down arrow keys in their search box behave differently to every other text field in the system.
There's a lot more to government than military intelligence gathering and law enforcement (although it would be a good idea for someone to remind most current governments that those are two things, not one). And most government projects end up spending insane budgets. This isn't limited to the US. It amazes me how often government projects to build databases to store a few million records with a few tens to thousands of queries per second (i.e. the kind of workload that you could run with off-the-shelf software on a relatively low-spec server) end up costing millions. Even with someone designing a pretty web-based GUI, people paid to manually enter all of the data from existing paper records, and 10 years of off-site redundancy, I often can't see where the money could have gone. Large companies often manage to do the same sort of thing.
The one thing that the US does well in terms of tech spending is mandate that the big company that wins the project should subcontract a certain percentage to small businesses. A lot of tech startups have got their big breaks from this rule.
Neither am I willing to take the word of some random dude on the Internet. Barring any more proof, I don't think we should be putting any stock in this.