71 karma · joined April 1, 2013
There were 1960s race riots in Bed-Stuy too.
In these places in prime Brooklyn what happened in the 1960s is divorced from the neighborhood's origins. Taking one unique case in Harlem and extrapolating it to gentrification all over NYC does not hold water. From my personal experience, it seems Harlem has seen the least amount of gentrification compared to these Brooklyn neighborhoods. If you were to take real-estate prices as a metric (you could choose others I'm sure), Brooklyn has far outpaced Harlem in the rate of change, especially in the last decade.
Do not take my comments out of context. You're making my argument but acting like current residents have more credibility - they don't. They are not the "artifacts" and living through race riots does not have any relevance whatsoever.
In my neighborhood "gentrifiers" are coming and preserving 1890s brownstones, on which a new facade costs upwards of 300k (yes hundreds of thousands). Maintaining our architectural history is not cheap and I think it's great that it's happening.
I find your position absurd.
IMO, current residents have no more of a right to live somewhere than any newcomer.
This does not explicitly suggest vulnerabilities exist in older versions, but rather the latest version with these changes is very explicitly insecure and should not be used. This does leave room for issues to have been discovered in old versions - maybe rather than fix, they are throwing in the towel.
The problem with the networks comcast and others currently maintain is they are saturated. And I'm not getting what I pay for as a result. They need a new pricing structure that properly values their product (bandwidth) and charges me for it.
Can anyone explain why the ISPs don't go down this road?
"JavaScript does not enforce private state, but it’s easy to write well-encapsulated programs: simply avoid having one object directly manipulate another object’s properties. Forty years after Smalltalk was invented, this is a well-understood principle."
However, the author doesn't seem to really understand this as he makes the case that access to private state and behavior of a "superclass" violates encapsulation:
"In JavaScript (and other languages in the same family), classes and subclasses share access to the object’s private properties. It is not possible to change an implementation detail for Account without carefully checking every single subclass and the code depending on those subclasses to see if our internal, “private” change will break them."
Well, yes they do allow access, but that doesn't mean you have to use it! This is considered bad practice when extending any class in other languages that I'm familiar with (C++, Ruby). Please take some of your own advice.
I do agree that hierarchies do not fit the real world as well the contrived examples from my first OOP classes and they should be used with extreme caution. Let's not throw out the baby with the bath water, however.
I am arguing FOR a capitalist system. I'm saying I don't understand why the article authors will assume it is going to break down because of technological advances. It has not thus far.
Edit: I see that my second statement in my first reply is poorly written. I meant "this" to refer to technological advancement, not to joblessness.
It looks like technology will continue to allow more and more people to pursue business ventures that are less and less related to filling basic needs. We will still consume, we will still find ways to trade that are mutually beneficial. We will simply have a better standard of living. It seems the logical conclusion is that there will be more opportunity for everyone, not less.
Different jobs and different opportunity is not the same as no jobs and no opportunity.
Let's not throw the baby out with the bathwater. There are ways of protecting your kids while still giving them the access that can seed a lifetime of curiosity.
"If you’re a great programmer, you make all the routines depend on each other, so little mistakes can really hurt you."
I know things were different back then, and Bill did not have the luxury of building on the wisdom learned over decades of experience, but 'separation of concerns' and 'loose coupling' have been central to every design decision I've made. It's hard to conceive of how one would believe that a tightly coupled, brittle design was a good one.