That's a good description, but everyone is still missing the actual cause. Firstly, the European Union is founded on an ideology that doesn't allow for an economic crisis. Second, when the crisis hit in 2008, the Greek *private* sector *reduced* their bank borrowing. Their money supply shrank, velocity shrank too, jobs were lost, tax receipts went down. Their government debt ratio went up, not because they were borrowing more, but because GDP fell. But the Euro doesn't allow Greece to run a large deficit, nor to increase their debt level, so they can't stimulate their economy to prevent further job losses.
The Greek government weren't in good shape before, but the combination of a crisis and the rules imposed by the Union have wiped them out.
maybe there is some security flaw with DHE that I haven't read about yet and that is why its turned off
Logjam. TLDR; about 100k hours of CPU time can build a dictionary to crack most session keys in less than 90 seconds for 512bit primes.
Have you looked at a graph of Greece's unemployment? It's jumped from <10% to >25% since the crisis began.
They need to increase the flow of money around the economy to stimulate job growth. During a downturn the velocity of money shrinks, so no free win there. It's unlikely they're going to increase exports, so a trade surplus is unlikely. They won't be borrowing more money from the banking sector any time soon. Which only leaves a government deficit to stimulate the economy, which is prevented by the Maastricht treaty.
Without leaving the Euro, Greece is screwed.
A real recovery, one for more than just the 1%, would be greatly appreciated.
Not gonna happen until all the private debt we've accumulated in the last 50 years is gone.
Everyone works with their files locally, changes are synced via a common server. Everyone has a compressed backup of the complete history of the entire filesystem for disaster recovery. Everyone should be able to browse and recover any version of any file without adding load to the server, though usability might be slightly lacking. You could also setup a FUSE filesystem on a linux box to browse the history.
You may need to partition the file storage into multiple repositories, so that people don't need to synchronise folders that they don't use.
You can hide the videos with a simple adblock filter; "slashdot.org##article#firehose-000".
You could also make the share button go away (slashdot.org##div.popularity), but that does break the tags css.
And in C not just the result, but the behaviour is undefined. If you divide by zero the compiler, runtime libraries and the CPU can do whatever they like. They could ignore you, crash, format your hard drive or kill your pet.
For speed reasons, this is a good thing. If it looks like you might run into undefined behaviour, the compiler can assume that the inputs to the program won't trigger that behaviour. This allows all kinds of optimisations to be performed, from dead code elimination, to hoisting invariant code out of loops.
At least other high level languages define precisely what a divide by zero should do. That way you run into platform or compiler specific heisenbugs far less frequently.
The drive's media wear indicator ran out shortly after 700TB, signaling that the NAND's write tolerance had been exceeded. Intel doesn't have confidence in the drive at that point, so the 335 Series is designed to shift into read-only mode and then to brick itself when the power is cycled. Despite suffering just one reallocated sector, our sample dutifully followed the script. Data was accessible until a reboot prompted the drive to swallow its virtual cyanide pill.