background preloader

Sortir de l’euro ?, par Frédéric Lordon (Le Monde diplomatique, août 2013)

Sortir de l’euro ?, par Frédéric Lordon (Le Monde diplomatique, août 2013)
Beaucoup, notamment à gauche, continuent de croire qu’on va changer l’euro. Qu’on va passer de l’euro austéritaire présent à un euro enfin rénové, progressiste et social. Cela n’arrivera pas. Il suffirait d’évoquer l’absence de tout levier politique en l’état d’incrustation institutionnelle de l’actuelle union monétaire européenne pour s’en faire une première idée. Mais cette impossibilité tient surtout à un argument beaucoup plus fort, qui s’exprime à la manière d’un syllogisme. Majeure : l’euro actuel procède d’une construction qui a eu pour effet, et même pour intention, de donner toute satisfaction aux marchés de capitaux et d’organiser leur emprise sur les politiques économiques européennes (1). La gauche-qui-continue-d’y-croire n’a donc le choix qu’entre l’impuissance indéfinie… ou bien l’advenue de cela même qu’elle prétend vouloir éviter (le retour aux monnaies nationales), sitôt que son projet de transformation de l’euro commencerait à être pris au sérieux !

http://www.monde-diplomatique.fr/2013/08/LORDON/49561

Related:  to read

mobile.nytimes Until now, every warning about an imminent breakup of the euro has proved wrong. Governments, whatever they said during the election, give in to the demands of the troika; meanwhile, the ECB steps in to calm the markets. This process has held the currency together, but it has also perpetuated deeply destructive austerity — don’t let a few quarters of modest growth in some debtors obscure the immense cost of five years of mass unemployment. As a political matter, the big losers from this process have been the parties of the center-left, whose acquiescence in harsh austerity — and hence abandonment of whatever they supposedly stood for — does them far more damage than similar policies do to the center-right.

Fenzo: OSS Scheduler for Apache Mesos Frameworks Bringing Netflix to our millions of subscribers is no easy task. The product comprises dozens of services in our distributed environment, each of which is operating a critical component to the experience while constantly evolving with new functionality. Optimizing the launch of these services is essential for both the stability of the customer experience as well as overall performance and costs. Probabilistically Bounded Staleness for Practical Partial Quorums Probabilistically Bounded Staleness for Practical Partial Quorums – Bailis et al. 2012, and Quantifying Eventual Consistency with PBS – Bailis et al. 2014 ‘Probabilistically Bounded Staleness… ‘ was the original VLDB ’12 paper, and then the authors were invited to submit an extended version to the VLDB Journal (‘Quantifying Eventual Consistency…’) which was published in 2013/14. The journal paper changed some of the terminology used to model staleness (how out of date the data you see might be) to relate more strongly to earlier research in the space. I’m going to work mostly from the original 2012 edition here – as a standalone paper I find it more intuitive – and reference a few parts from the extended edition as needed. Let’s start by unpacking the title a little.

Functional Programming should be your #1 priority for 2015 You probably have heard expressions like “Clojure”, “Scala”, “Erlang” or even “Java now has lambdas”. And you might know it has something to do with "Functional Programming". If you’re participating to any Programming Community, this subject probably has popped up already. The Software Revolution In human history, there have been three great technological revolutions and many smaller ones. The three great ones are the agricultural revolution, the industrial revolution, and the one we are now in the middle of—the software revolution. [1] The great technological revolutions have affected what most people do every day and how society is structured. The previous one, the industrial revolution, created lots of jobs because the new technology required huge numbers of humans to run it.

What's new in CPUs since the 80s and how does it affect programmers? This is a response to the following question from David Albert: My mental model of CPUs is stuck in the 1980s: basically boxes that do arithmetic, logic, bit twiddling and shifting, and loading and storing things in memory. I’m vaguely aware of various newer developments like vector instructions (SIMD) and the idea that newer CPUs have support for virtualization (though I have no idea what that means in practice).What cool developments have I been missing? What can today’s CPU do that last year’s CPU couldn’t? How about a CPU from two years ago, five years ago, or ten years ago? Introducing Dynomite - Making Non-Distributed Databases, Distributed Netflix has long been a proponent of the microservices model. This model offers higher-availability, resiliency to failure and loose coupling. The downside to such an architecture is the potential for a latent user experience. Every time a customer loads up a homepage or starts to stream a movie, there are a number of microservices involved to complete that request. Most of these microservices use some kind of stateful system to store and serve data. A few milliseconds here and there can add up quickly and result in a multi-second response time.

Why Cards Are the Future of the Web We are currently witnessing a re-architecture of the web, away from pages and destinations, towards completely personalised experiences built on an aggregation of many individual pieces of content. Content being broken down into individual components and re-aggregated is the result of the rise of mobile technologies, billions of screens of all shapes and sizes, and unprecedented access to data from all kinds of sources through APIs and SDKs. This is driving the web away from many pages of content linked together, towards individual pieces of content aggregated together into one experience.

Related: