And how long is that excuse valid for? It's not like Europe has been very peaceful and tripped Africa up on purpose, we've started two world wars in the last 100 years on our own turf. Yes, I realize problems don't go away in a day or a year or even a decade but look how far Europe has come in the last 70 years. How far has Africa come? How much aid money, emergency relief, how many education and healthcare programs have they gotten for free?

Still trotting out that old excuse and blaming the white man for all their woes is probably going to backfire. It only nourishes the people who think Africa is the way it is because they're primitive deadbeats who can't get anything done on their own. It's not that there's anything wrong with the people as such, take a black man and put him in a different environment and he might end up as President and a Harvard magna cum laude graduate.

My impression is that most of Africa's problems are cultural, like for example the response to Ebola. If they'd just stop touching their dead and seek medical help they'd do fine, but through ignorance and indifference and working against those trying to help them they'll just let it spread. Like HIV, there's a reason it's a huge problem south of Sahara and practically nowhere else and it's because for some cultural reason they just don't seem to value safe sex.

Actually, most religions claim there's an abundance of ways to fall for temptation and sin while the path to God is straight and narrow. You make it sound like making it a challenge and pointing out all the alternatives and benefits would be a good thing, while the religious consider it trying to lead the children astray and trying to put a wedge between them and God. Like say their interpretation of the Bible means sex belongs only in the marriage - bear with me on this one - then pointing out that "if you're going to have sex anyway, use a condom" is kinda upselling a sin. It leaves the impression they don't really think you'll stick with plan A anyway. So a lot of parent don't want their children to know there even is a choice. You think in terms of pros and cons, they think it's one good choice and a lot of bad alternatives they don't need to know about..

I think you need to distinguish between terrorism and reign of terror. Hit-and-run bombings like the IRA or ETA rarely succeed in people giving in to terror. Taking actual control of areas, waving the flags and killing off all that oppose you has a much better historical record, ask anyone from Pol Pot to Hitler and Lenin and Mao. In case you haven't noticed, they're using their brutal savagery primarily to quell resistance and internal dissent. The story they're selling is that they're too fucking crazy to pick a fight with and so far they seem more than willing to put that reputation to the test and post it on YouTube.

I mean, would you like to be in a resistance movement inside IS territory? Do they care that they can't find you? Heck no, they'll just round up a few civilians and shoot them in retaliation for your sabotage/assassination/sedition. Far more civilized occupants have used that tactic, all those millions of people they control are in practice hostages. You're fighting an enemy willing to overreact to any provocation, give them a push and you won't get a shove back they'll beat you to a bloody pulp. And given their history so far, I don't think they have a problem with human shields. You can not excise them without massive civilian casualties. Sadly I give them much better odds than you predict.

FYI, North Korea has made three underground nuclear detonations in 2006, 2009 and 2013. Very few doubt that they now got a few nukes in the kiloton range - basically 1940s tech - and the means to deliver them to Seoul - a mere 35 miles away from the NK border. China doesn't care. They got a loyal ally, they could crush him at any moment and it'd only create hostility between Koreans and Chinese. And the country is not worth the trouble. I guess if China ever went on the offensive they'd gobble up NK - and probably SK too - but only if they're on the warpath anyway.

And? Part of being a cross-platform toolkit is that you must keep up with the underlying platforms, if you start failing to look native or behave native or integrate nicely or lack interfaces to new functionality you'll quickly cease to be useful for that. It'll still function as a toolkit for building KDE though since they define their own native, but then it will gravitate back towards being a Linux-only thing.

P.S. Despite Qt being cross-platform, most KDE SC applications don't seem to be. There's been an ongoing project to make them cross-platform for years, but many still have trouble compiling or working correctly.

Well, you must also know the HTML entities, even in plain text mode... writing æøå doesn't work, but æøå works. In this case µ doesn't work though. And I think all languages have Unicode support good enough to strip control characters and shit if you're not lazy. My impression was that it was more to sabotage the ASCII "art" than anything else.

Well, sometimes they make convenient little assumptions about the write amplification and other things in coming up with that number. Also it's the number they use for warranty claims, so it may not reflect the kind of endurance you'd normally expect. The latest trick is to basically use part of your drive as a semi-permanent SLC cache and only write it to MLC/TLC NAND later, if ever so what you actually get will depend on your usage pattern. If you just keep on rewriting a small file it'll probably not leave SLC at all, while if you use it as a scratch disk filling it up with large files and emptying it you'll hit the MLC/TLC hard. The rating is just to give consumers who don't want an in-depth look something to relate to.

Personally my first idea was, if they can deliver us a MLC drive at 45 cents/GB doesn't that mean they should be able to deliver us a SLC drive at 90 cents/GB? That's not disturbingly much, considerably faster and should have all the endurance you'll ever need. That said, TechReport got 3 (out of 6) consumer drives they've written >1 PB to, so I'm guessing most drives fail from something else than NAND exhaustion. And I don't reinstall my OS disk every day.... I just checked and I've used up 50 of my 3000 P/E cycles after 150 days of 24x7 running so at this rate it should take 25 years.

I know people who turn on their computer maybe 2-3 hours a day on average, just streaming no heavy media usage. Any SSD will last them forever, it's all about $/GB. Now if you want a guess they said 5000 P/E -> 3000 P/E (60%) for 25nm -> 20nm MLC, so I'm guessing 3000 * 0.6 = 1800 P/E for 16nm. And TLC is probably like 500 P/E, though this drive doesn't use that.

Because C.

In other words pretty much exactly what some tried to say when Google first launched Chrome, except for OSS zealots who were blinded by their Mozilla support and "do no evil" slogan.

For Google open source is not a goal, it's a tool. Google funded Mozilla to run a browser war by proxy, as an open source and non-profit organization Mozilla could get massive support from organizations and volunteers that Google never could and a much higher tolerance of bugs and broken functionality. And I mean that both with respect to internal bugs as well as broken web sites due to MSIE-only code. As a means to an end to push a standards compliant web for Google to profit from it was a success.

With Android Google again used open source as a battering ram against an entrenched monopoly, this time against Apple in smart phones. Once again a host of unlikely allies - pretty much everyone except Apple and Nokia, really - jumped on board along with the open source rah-rah and low cost clone manufacturers looking to get a free ride. That you could have things like CyanogenMod and get root on your phone was new - even though some manufacturers blocked that it was a step up from the all-closed platforms.

I'm not saying those are bad things, but those mutually beneficial interests come to an end. Once we've been released from the old stranglehold, Google wants to make a new one with themselves in control. I don't think I can make a catchy acronym for it like embrace-extend-extinguish but it goes something like commodify-bundle-obsolete:

1. Commodify the functionality through open source
2. Bundle it with Google APIs/services
3. Let the open source version toil in obsolescence

Search results are still a major driver of Google's revenue. The default search engine is defined by your browser, the default browser is defined by the platform so from their perspective pushing Android and Chrome both makes very much sense - if you're using a Google product you'll never be pointed anywhere but a Google service. Chrome is also a vital part of that "all-or-nothing" bundle Google is selling to make companies use Google Play which is now their second cash cow.

Firefox is no longer a partner against MSIE, they're a threat against the OHA bundle. If you can take AOSP and install Firefox with no further strings attached that's one of the many pieces you need to replace filled. The less alternatives you have, the more power Google has over the Android ecosystem. If you're still stuck in the mindset where MSIE had 95% market share you'll fail to see that your one-time ally is no longer on your team. They're on their own team, as every for-profit company eventually end up being.

Native speakers, yes. But whether you're in China or India or Spain the most popular second language is English. Functionally you're much better off because at almost any tourist destination you'll find somebody speaking English, while Mandarin is great if you go to China and pretty much useless everywhere else. English got presence in Europe (UK + EU really), North America (USA), Asia (India), Oceania (Australia) and Africa (several former colonies). I'm not going to argue the moral side of colonialism, just say that practically it's the only language with global reach.

The quality of the English version is what it is. The quality of the non-English version is what it is plus all that was lost in translation, it's certainly not going to be better. The worst is when they move around on standard shortcuts, for example in MS Office all English versions has Ctrl-F as Find and Ctrl-B as Bold. In Norwegian Ctrl-F = Bold (Fet) and Ctrl-B is Find (Finn) and I absolutely hate it every time. And yet in the interest of sanity they do keep other English shortcuts like Ctrl-S = Save (Lagre), even though that makes no sense in Norwegian. Never mind that when you're working with code or databases there is no Norwegian C# nor SQL, so it all ends up rather Norwenglish when you try.

Don't get me wrong, I'm fond of my language when it comes to identity and culture. But when it comes to communication having global terminology and one way of doing it makes everything so much simpler. Yes, there's a whole lot of "English" speakers out there but any resemblance of a common tongue beats trying to use translators. It's something of a first world issue though as 16% of the world is still illiterate in their first language but I hope that in 100 years you could talk to at least half the world's population in one language.

Try not stealing one since the US government doesn't own them and I think you'll find yourself in jail. Any takers who'd like to bet otherwise? I think in practice this is resolved already, what you bring back to Earth is yours. The fun parts would be that nobody has mining rights, if you find a big gold vein there's nothing stopping another country/company dropping a mining rig right next to yours.

This must be the most clueless post about the 1000/1024 divide so far. It never had anything to do with the computer's performance, it's that when you build a digital computer a lot of things will be sizes of two because what you can address with n bytes will be 2^n. Physical memory, memory pages, caches, buffers, floppy and hard drive sectors all the "microunits" in the computer are powers of two. Hint: No actual hard drive gives you 1MB = 1000000 bytes because it's not divisible with 512, in reality they give you 1954*512 = 1000448 so they don't underdeliver. Actually make that divisible by 4096 for modern HDD drives with 4K (no, not 1000) sectors.

There is a single reason why computer scientists usurped the prefix kilo and that is because they needed to describe "one thousand and twenty four bytes" - or multiples of that - very, very often. They needed a shorter name, they never needed the unit "1000 bytes" and so "one kilobyte" became their shorthand for 1024 bytes. And unless you're really good at doing math in your head, tell me how much is seven kilobytes exactly? (And if you answer 7000 I'll slap you). We still say 512GB of RAM. Nobody wants to say 549.755813888 GB of RAM, because multiply that with a billion and you have how many bytes that is. It's not some nice, round number.

Either way you're going to run into some f*cked up conversions if you mix GiB and GB, which I'll use now for clarity. If you have 512GiB of RAM (hey, servers do) and load 512GB from disk, how much of your RAM have you used up? Now while you're calculating that, this other person who uses a GiB system says so that was like ~477 GiB so like ~35 GiB free? Or you have to say you have 549.8 (rounded) GB RAM and use exactly 512 GB. Of course in reality file sizes are probably a rather random size so you'll have two long floating point numbers. At least with base 2 you just have one, because you have exactly 512 GiB RAM.

And when you do have base 2 numbers then multiplication/division gives other nice base 2 numbers like 10 MiB / 2 KiB = 5 KiB. 10.485760 MB / 2.048 KB = how much? It's a lot uglier if you numbers are 2^n values, which again they will be a lot of the time. At least far more often than base 10 as long as you're working with the computer itself and not business data or whatever. If you for example want to make something fit in L3 cache to optimize and algorithm, the numbers will be in base 2. You can't "bugfix" your way out of that.

Well I seem to be both right and wrong, it's 42 bits from the camera but it's losslessly compressed so an actual RAW file is still around 70 MB/photo (listed under cons) so the card does hold 70,000+ photos.

So the highest MP camera I could find in a normal store is 40 Mpix (Pentax 645D) * 14 bit RAW = 70MB/picture. So good for 70,000+ photos. Or the Panasonic HC-X1000 4K/24 & UHD/60p camera just released, 150 Mbps = 7-8 hours continuous recording. But I suppose it's good for when you want to carry 10 BluRays in your phone. Whoops, wrong format not microSDXC. I guess there's a niche for this since they made it, but I kinda fail to see the target market, unless it's the "give me the biggest and best you got" crowd.