Hacker Newsnew | past | comments | ask | show | jobs | submit | vampolo's commentslogin

It might feel empowering demanding taxes to be spent in the richer areas instead of helping poorer areas: Zaia, Governor of Veneto and member of the anti-Europe, anti-Euro, anti-italian nation Lega Nord party, promoted the referendum demanding that "taxes in Veneto should stay here, not helping Sicily".

It probably is, at first. But in an economy of different parties, who produces more needs some buyers to keep growing. If there are not enough buyers, overproduction and economical collapse will knock at the door. You can see this trend internationally: we seldom see a country be an outlier in the yearly growth. Either all countries grow, or all countries decline. It is the % that changes. We saw this during the 2008-2012 crisis in particular.

It is in the interest of the richest areas to help the poorest. By doing so not only the average quality of life of a country increases. With less economical inequalities between regions, the once poorer regions are buyers of goods of the once richer ones.

While you correctly associated Lombardia and Veneto to Germany, you forgot to mention that after the WWII, Germany went split politically and economically. When it got re-united in 1989-1991 East Germany was economically very diverse from the more developed West. Our fathers were wiser: instead of doing referendum demanding taxes to be withheld in the West, they demanded to be taxed to help the East. [source https://en.wikipedia.org/wiki/German_reunification#Cost_of_r... ] After 20 years those differences are still somewhat visible, yet they do not constitute a problem for Germany's growth and quality of life as a nation.

On the historical side it has been confirmed that 2/3 of the gold resources in Italy came from Regno delle due Sicilie [source: https://it.wikipedia.org/wiki/Regno_delle_Due_Sicilie in Patrimonio e finanza section ]. Those lands are today's most rural parts of Italy, yet contributed the most to the wealth of Italy as a nation.

I highly suggest a read on this last historical matter: Terroni by Pino Aprile. You might find a different point of view. [ https://www.amazon.com/Terroni-Ensure-Italians-Became-Southe... ]


> It is in the interest of the richest areas to help the poorest.

Yes, however one still needs to decide to which extent. Italy helps the poorest areas much more than Germany or the US do. Would a federal model like Germany work better?

That's why I said that redistribution is OK in principle, but many feel that in Italy there's just too much of it.

> On the historical side it has been confirmed that 2/3 of the gold resources in Italy came from Regno delle due Sicilie

Many wrongs were commited in that age, many of which targeted the North, as well.

However, if you sum all the subsidies the South has been granted through the years (one among many: Cassa per il Mezzogiorno) that would easily offset those gold resources.

Edit: actually is more, Cassa per il Mezzogiorno was given about 140 billions, while 2/3 of Italy's gold resources are worth about 100 billions. One should also keep in mind that Cassa per il Mezzogiorno was active only between 1950 and 1984, and many other subsidies for the South were present before, during and after.


> That's why I said that redistribution is OK in principle, but many feel that in Italy there's just too much of it.

While the amount is huge, that is not event the biggest issue. What people resent is _how_ that money is spent: public construction project meant mostly to funnel money to organized crime and companies of relatives of politicians; covering the bizarre expenses of the politicians; and the never ending legion of public employees that got a job in exchange of votes (but get paid without working much or at all). If you add the fact that southern Italy is where most of tax evasion and health-related fraud occurs, the feeling for many is not that they are paying to help the poorer, but that they are sweating so that others can live a comfortable life.

While it is not a black-white situation (there are also such issues in the North, and hard working people in the South), the difference is notable.


Nice article but i think it touches two problems, but then offers a solution to one.

Every program has a code structure. Certain programs have better code structure than others. These are properties independent from the programming language. Javascript evolved from a single entry point, being the [in]famous $.ready() to set behaviors of some html elements, to full blows ES6 single page applications.

It all started as a toy language.

But it simplicity is also its flaw: it enables every human with a not so deep understanding of computer architecture to write a button that changes color on click. The absence of a type system and a solid class paradigm (introduced in ES6) spoiled programmers to pass any object down to any function breaking well known software paradigms: Law of Demeter (https://en.wikipedia.org/wiki/Law_of_Demeter), Open/Close Principle (https://en.wikipedia.org/wiki/Open/closed_principle) and the Liskov Substitution Principle (https://en.wikipedia.org/wiki/Liskov_substitution_principle).

I'm in the Web space professionally from 15+ years and those are the 3 rules i see JS devs break the most, generating complected code (for more understanding of the term have a look at https://www.infoq.com/presentations/Simple-Made-Easy ), hard to maintain and extend like the example shown in this article.

The advice to build interfaces around data structures, proposed as solution, is no different than the Liskov Substitution Principle.

The other problem the article cites is the event loop.

At the time o $.ready() there was no event loop. Developers were just attaching functions to user events: clicks, hovers, blurs, focus. Just a direct mapping between an element and a function. You can simply come to the conclusion that the trigger and the action to be performed were not loosely coupled, but indeed tight together. Easy, yet not scalable.

Tieing events to the dom structure was another sin opening more questions: should an element that is not interactable fire events? bubble them ? every browser had its own answer to those questions. Things got even more complicated with single page applications which html element in the page can be added and removed. So here comes the event loop, like other well known ui stacks did in the past.

The concept of an event loop is not a novelty, it is indeed bound to the architecture of our computer: clock cycle, interrupts, kernel events. In the case of windows is the well known WPF (https://en.wikipedia.org/wiki/Windows_Presentation_Foundatio...) which has, among a lot of other things like any Microsoft product, the concept of a dispatcher that is central to the flux architecture.

In 2015/2016 with React/Flux Javascript and the Web is moving out of puberty, enabling developers to write clean, decoupled, extensible code. Thus no all devs are ready to grasp those architecture that are so obvious in other ecosystems. To cite Poul-Henning Kamp in A generation lost in the bazaar (http://queue.acm.org/detail.cfm?id=2349257):

"So far they have all failed spectacularly, because the generation of lost dot-com wunderkinder in the bazaar has never seen a cathedral and therefore cannot even imagine why you would want one in the first place, much less what it should look like. It is a sad irony, indeed, that those who most need to read it may find The Design of Design entirely incomprehensible."

my 2 cents


Oh! i see! So you are the guy that DDoSed github by downloading Ember!


I thought the point of heavy client-side frameworks was to take load off the server.


Is this log public available ? I would like to dig into it.


This Google Doc has a list of URLs tested by the detectify.com scanner:

https://docs.google.com/document/d/1vN2QOG2OZIAHGXDmd5wB8FPi...


I wouldn't use a program B to circumvent a bug of another program A if not in a exceptional case in which patch of program A cannot be created.

This is exactly the case. If bash has a bug. that must be fixed. And it has been done already. Just update bash in major distributions and the bug is gone.

But still you want to have a tool like sysdig to detect if your system has already been compromised previously and it is out of sysadmin control.


No problems on an ubuntu 14.04 with chromium


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: