What's different about thin client computing this time around is that internet is ubiquitous and wireless.
Which is going to lead to a lot of frustrating design decisions. 10 years ago, in the heyday of Flash based "thin clients", offline support was something that everyone considered important, because people travel with their laptops and need to get work done on the road. Now, with the internet considered ubiquitous, and frameworks that tried to deal with disconnected use-cases like Google Gears declared dead, people using web applications are going to experience catastrophic data loss when the train they're on goes into a tunnel as a sibling post pointed out, or even in urban canyons where cellular coverage can be a bit patchy due to direct signals being blocked and excessive multipath reflected off the surrounding buildings.
You forgot to mention that each time the cycle goes around, last time's "thin clients" are now the "fat clients" that are getting replaced.
The only thing changing here is the way terminology is being applied. 10 years ago, Flash based thin clients were coming to replace your native code fat clients, giving the benefit of zero-install without the clunkiness of HTML and Javascript. Now that HTML and Javascript are no longer clunky (partly because computers are now much faster, so you don't notice the clunkiness, and partly because HTML5 brings some useful features for web applications), pure web applications are having their day.
On to the story at hand: there is no doubt that the wider handset market is in all kinds of trouble. Apple clearly makes most of the profit, and Samsung picks off what is left. What does this leave the other players? Nothing.
From observing a number of industries over the years, I've come to the conclusion that mature markets seem to gravitate towards 3 major players (usually the third one is far behind the first two, sometimes there is one clear leader and two far behind it), and a bunch of also-rans that mostly churn away from startup to bankrupcy in the race to join the boom market, with a few niche players or well funded branches of bigger companies managing to stay around long term without being particularly successful. Occasionally one of these also-rans will move up the ranks, which signals the death of the third placeholder, and possibly a major shift in that industry with the possiblity of all three top players quickly fading away due to entrenched ideas that prevent them adapting to the shift quickly (eg Nokia, Ericsson, Motorola -> Nokia, Blackberry, Apple -> Apple, Samsung, HTC).
The oil embargo was the direct reason why Japan needed to expand their empire into the oil fields of the South China Sea in order to continue with their occupation of Northern China and Korea. And the US presence in that region was the reason why Japan launched a surprise preemptive attack on Pearl Harbor. So you could say that the oil embargo was a major cause of the war between Japan and US, just as the cyberattacks on Iran could be enough provocation to send them over the edge this time around.
Certain organizations and individuals are subject to trade sanctions, embargoes and other restrictions under U.S. law. These restrictions apply to both domestic and foreign transactions.
Meanwhile, the Iranian nuclear industry has no problems getting the equipment it needs (albeit with a few carefully targetted viruses), while farmers and students get to suck on the sharp end of UN trade sanctions.
While the actions of the Apple store employee were correct according to the law, I hope this gives some publicity to the fact that sanctions do not work for their intended purpose, and only hurt the innocent civilian population in the country of their target.
Could another possible explanation be the fact that a significant portion of trade has moved from USD based to Euro based, and the poor performance of the Euro recently is pulling the USD price down?
There's speculation that their accepting of Bitcoin inadvertantly categorised them as a gambling website.... It does not seem malicious or incompetent that this mistake happened.
read a random tour book for Southern Europe and you are likely to see warnings about Gypsy/Roma pickpockets included
Go on a tour of Southern Europe, and you'll likely see evidence that those warnings are there for a good reason. The warnings themselves are not directly due to racism, though the continued lack of opportunities for Roma to break out of this underworld likely do have a lot to do with racism.
The notion of pure ethnic groups is a fiction, but you can trace some kinds of population lineages using genetic markers.
Right, but the product of such tracing should be a report full of probabilities and giving a "most likely origin" type conclusion, not a certificate stating that someone is conclusively not Roma or a Jew.
Also, he didn't find his genetic racial disposition, he focused on "proving" he wasn't descended from two particular racial groups, neither of which is defined exclusively by their genetic makeup.
The problem is not that the tests were carried out, it is that the testing facility issued a certificate stating something that their tests cannot conclusively prove, and even if they could prove it, it would go against medical ethics to issue such a certificate, as the document has no ethical use.
The binary was probably cached. The GP was speculating about doing too much of computation on things that make it an IDE (or an OS) than a simple text editor. What is read off disk was not part of what I was testing, but Emacs does not need to read any.el or.elc files to start up. But anyway, a cold start on this machine is about 2.5s real time, including spinning up the disk.
Cheese. The heavily processed type that comes in individually wrapped slices that are barely distinguishable from the plastic they are wrapped in. The choreography is of similar quality to the music. I can only guess that the product they're promoting is along the same lines. Nice example of how the bungled efforts of one small regional office can completely wreck your global product launch.
It sounds like Korea has taken the same route as Japan. NTT and Softbank Wifi networks everywhere, but you have to be a subscriber to connect. Absolutely useless for visitors, who are more in need of public WiFi due to the extortionate rates phone companies charge for data roaming outside the EU.
Finally, while oyster works very well for people who use it regularly, it's surprisingly easy to get caught out and charged a "maximum fare" - one example where you have to be careful - I entered the central line the night before last and just as I entered there was warnings of flooding and major delays and "you are advised to take a bus". Had I turned around and walked straight back out again I would have been charged a £7 maximum fare. Armed with this knowledge I ignored the advice being given and forced my way onto the next train.
On the contrary, unlike a paper ticket, refunds are usually automatic when incidents like this happen, and when the system does not automatically link the known disruption to the open journey, its a simple over the counter transaction to get the refund, while on a paper ticket you have to fill out a form and send it to TFL for a refund which comes as a cheque in the mail around a month later.
On the Google IPv6 statistics, it says in Romania IPv6 is faster than IPv4.
Interesting, they must have good IPv6 peering arrangements set up in Europe already.
I have had an IPv6 tunnel working since last IPv6 day, with an exit point in Australia. On Wednesday I tried a traceroute6 to google.com and saw that it picked a server in Google-AP (Asia Pacific) as the end destination (same as IPv4), but to get there, it went via the US, onto Google's network there. So I can see why users in Japan might have been seeing latency issues.
Slashdot Mirror
I suspect this accounts for the majority of "Java backwards incompatibilities".
Which is going to lead to a lot of frustrating design decisions. 10 years ago, in the heyday of Flash based "thin clients", offline support was something that everyone considered important, because people travel with their laptops and need to get work done on the road. Now, with the internet considered ubiquitous, and frameworks that tried to deal with disconnected use-cases like Google Gears declared dead, people using web applications are going to experience catastrophic data loss when the train they're on goes into a tunnel as a sibling post pointed out, or even in urban canyons where cellular coverage can be a bit patchy due to direct signals being blocked and excessive multipath reflected off the surrounding buildings.
You forgot to mention that each time the cycle goes around, last time's "thin clients" are now the "fat clients" that are getting replaced. The only thing changing here is the way terminology is being applied. 10 years ago, Flash based thin clients were coming to replace your native code fat clients, giving the benefit of zero-install without the clunkiness of HTML and Javascript. Now that HTML and Javascript are no longer clunky (partly because computers are now much faster, so you don't notice the clunkiness, and partly because HTML5 brings some useful features for web applications), pure web applications are having their day.
From observing a number of industries over the years, I've come to the conclusion that mature markets seem to gravitate towards 3 major players (usually the third one is far behind the first two, sometimes there is one clear leader and two far behind it), and a bunch of also-rans that mostly churn away from startup to bankrupcy in the race to join the boom market, with a few niche players or well funded branches of bigger companies managing to stay around long term without being particularly successful. Occasionally one of these also-rans will move up the ranks, which signals the death of the third placeholder, and possibly a major shift in that industry with the possiblity of all three top players quickly fading away due to entrenched ideas that prevent them adapting to the shift quickly (eg Nokia, Ericsson, Motorola -> Nokia, Blackberry, Apple -> Apple, Samsung, HTC).
FTFY.
The oil embargo was the direct reason why Japan needed to expand their empire into the oil fields of the South China Sea in order to continue with their occupation of Northern China and Korea. And the US presence in that region was the reason why Japan launched a surprise preemptive attack on Pearl Harbor. So you could say that the oil embargo was a major cause of the war between Japan and US, just as the cyberattacks on Iran could be enough provocation to send them over the edge this time around.
Was this girl a representative of "certain organizations and individuals"? ie, was she listed in the OFAC Specially Designated Nationals and Blocked Persons List, or representing an organization on the EAR Entity Chart?
Meanwhile, the Iranian nuclear industry has no problems getting the equipment it needs (albeit with a few carefully targetted viruses), while farmers and students get to suck on the sharp end of UN trade sanctions.
While the actions of the Apple store employee were correct according to the law, I hope this gives some publicity to the fact that sanctions do not work for their intended purpose, and only hurt the innocent civilian population in the country of their target.
Could another possible explanation be the fact that a significant portion of trade has moved from USD based to Euro based, and the poor performance of the Euro recently is pulling the USD price down?
That looks pretty incompetent to me.
Go on a tour of Southern Europe, and you'll likely see evidence that those warnings are there for a good reason. The warnings themselves are not directly due to racism, though the continued lack of opportunities for Roma to break out of this underworld likely do have a lot to do with racism.
Roma migrated to Europe from Northern India, which is outside the Neanderthal region.
Right, but the product of such tracing should be a report full of probabilities and giving a "most likely origin" type conclusion, not a certificate stating that someone is conclusively not Roma or a Jew.
Also, he didn't find his genetic racial disposition, he focused on "proving" he wasn't descended from two particular racial groups, neither of which is defined exclusively by their genetic makeup.
The problem is not that the tests were carried out, it is that the testing facility issued a certificate stating something that their tests cannot conclusively prove, and even if they could prove it, it would go against medical ethics to issue such a certificate, as the document has no ethical use.
Really? I always thought that Libertarian views came out of the nobles resenting paying taxes which get spent on improving the lives of the commoners.
s/vi/vim/g
The original vi can be matched by almost everything (the notable exception being Notepad.exe).
The binary was probably cached. The GP was speculating about doing too much of computation on things that make it an IDE (or an OS) than a simple text editor. What is read off disk was not part of what I was testing, but Emacs does not need to read any .el or .elc files to start up. But anyway, a cold start on this machine is about 2.5s real time, including spinning up the disk.
Cheese. The heavily processed type that comes in individually wrapped slices that are barely distinguishable from the plastic they are wrapped in. The choreography is of similar quality to the music. I can only guess that the product they're promoting is along the same lines. Nice example of how the bungled efforts of one small regional office can completely wreck your global product launch.
$ time emacs -nw -Q --eval "(kill-emacs)"
real 0m0.069s user 0m0.036s sys 0m0.012sIt sounds like Korea has taken the same route as Japan. NTT and Softbank Wifi networks everywhere, but you have to be a subscriber to connect. Absolutely useless for visitors, who are more in need of public WiFi due to the extortionate rates phone companies charge for data roaming outside the EU.
It's 0.8 miles to the Shepherds Bush Empire from Hammersmith Broadway. Easily walkable in 15 minutes.
On the contrary, unlike a paper ticket, refunds are usually automatic when incidents like this happen, and when the system does not automatically link the known disruption to the open journey, its a simple over the counter transaction to get the refund, while on a paper ticket you have to fill out a form and send it to TFL for a refund which comes as a cheque in the mail around a month later.
Aren't both Hammersmith and Shepherds Bush in zone 2?
Interesting, they must have good IPv6 peering arrangements set up in Europe already.
I have had an IPv6 tunnel working since last IPv6 day, with an exit point in Australia. On Wednesday I tried a traceroute6 to google.com and saw that it picked a server in Google-AP (Asia Pacific) as the end destination (same as IPv4), but to get there, it went via the US, onto Google's network there. So I can see why users in Japan might have been seeing latency issues.