The only real downside is that when I recommend Cox to friends, I have to be very careful how I say it.
1,445 karma · joined February 28, 2011
The only real downside is that when I recommend Cox to friends, I have to be very careful how I say it.
I suppose the NYT could argue that this article only reiterates what was previously reported on the ANT program, and the technology disclosed in that report is over 5 years old. Still, this article may get more attention because when ANT was previously reported the media (and much of HN) got distracted by the NSA's ability to jailbreak iPhones (in 2008!) and largely ignored the passive radio-based technology that was also described.
Enough with the semantic arguments:
1. Calling a servant an "au pair" or a "perk" doesn't make her less of a human being.
2. ALL human beings have rights, and in the US those rights include employment protections, such as a minimum wage.
3. It doesn't matter what "perks" the diplomat was promised. She cannot violate another's legal rights because she feels entitled to a servant (excuse me, an "au pair").
4. Shipping a human being overseas to be a servant with the expectation that they will be underpaid doesn't make this okay. On the contrary, that's ominously close to human trafficking.
5. Asking to be released from unjust and illegal labor conditions and proposing a settlement for back-pay and damages IS NOT BLACKMAIL! (If it were blackmail, why is the servant not being prosecuted for extortion? Answer: because it's not blackmail!)
6. The arrest really isn't about the servant (Ms. Richard). Ms. Khobragade is being prosecuted by the federal government for a crime committed against the federal government. She lied on a federal form, which is a felony right there. She also did so to cover up that she violated the minimum wage law. That's why she was arrested.
7. All the talk about servants that has arisen in Western media and online is due to India's response and how stunned we in the West are that there are still people on this planet who can be this inhumane (as your comment sadly illustrates).
Edit: Grammar fixes.
Yes, and it's annoying to have a long list of if statements. However, there's a blocks based alternative since iOS4/10.6, and a number of third-party variations.[1]
> KVO is string-ly typed
That's a big reason why libextobjc's @keypath() macro is so popular.[2]
> KVO requires you to handle superclasses yourself
That's a feature, not a bug. If you use observeValueForKeyPath:ofObject:change:context: then you need to call super just like overriding any other method. This also gives you the flexibility to selectively decide to override behavior of your own superclasses.
> KVO can crash when deregistering
Only if you deregister twice. And yes, it really sucks that you can accidentally deregister the same key path that a superclass deregisters, resulting in a crash. Much has been written about this issue, and third party libraries address it.[3]
> KVO is a pit of failure
That's a strong and subjective statement. Yes KVO can be frustrating for new developers - no argument there. But it does have its place.
> KVO is implicit
Woah, no one (including Apple) is suggesting that apps use KVO for all of their message passing and dependencies. It has its place, especially for monitoring changes to Apple's APIs or when multiple observers need to monitor the same object (again, that's a feature not a bug).
> KVO can cause infinite loops
Your handler should always avoid triggering the same event that triggered it. That's not unique to KVO.
> KVO is the old way
I remember when Apple introduced it, so I guess that makes me even older! Actually, Apple's KVO is responsible for some of the newest JS libraries. SproutCore borrowed many of KVO's ideas,[4] and you may be familiar with one of SproutCore's notable forks: Ember.js
> When is it okay to use KVO?
Agreed that these are great use cases for KVO. But doesn't this counter the title of the post? It's certainly not "harmful" to use KVO for these.
[1] https://github.com/search?l=Objective-C&q=kvo&source=cc&type...
[2] https://github.com/jspahrsummers/libextobjc/blob/master/exto...
[3] http://www.mikeash.com/pyblog/friday-qa-2012-03-02-key-value...
I don't see how they can advertise that it runs "top Android apps" & "latest Android apps" without supporting the Play Services APIs.
Sadly, there are still a lot of voters in the states who embrace American exceptionalism and are perfectly content with an NSA that targets foreigners so long as it keeps us safe. But it's another thing entirely for the FBI to turn around and deploy that same technology on its own citizens.
The FBI has a long history of abusing power, and they're not exactly popular with the political base of either pole. Their role in this needs to be included within the national discussion.
As I said, there are plenty of reasons to oppose deep sea trawling and I hope the ban is successful. But an infographic that implies that there are colorful Finding-Nemo-esque reefs a kilometer down with "roads, hospitals, kindergartens, dorms" doesn't help. It just makes supporters of the ban look naive.
There are a lot of reasons to oppose deep sea bottom trawling, but this infographic based on naive and erroneous assumptions may do more harm than good.
[1] http://www.coral.org/resources/about_coral_reefs/coral_overv...
> It’s not that hydraulic fracturing is new, it’s that it’s being used in new rocks, which means it’s being used in new places.
Only engineers and historians care whether fracking was first invented six decades ago or two decades ago. Either way, if it's suddenly being on new types of rocks, with new orientations of wells (horizontal), and in places it's never been done before, and on a exponentially greater scale -- then it absolutely feels like "a new, experimental technique that hasn’t been tested, isn’t regulated, and is being tried for the first time in your backyard."
> It is not a drilling technique... Hydraulic fracturing doesn’t take place until well after the well has been drilled, cased, and cemented. It is a completion technique, to stimulate the production of the well. This is not splitting hairs, it’s a big difference; get the facts right
In the public's mind it is splitting hairs. If the technology for fracking didn't exist, there wouldn't be all these new horizontal drilling rigs in people's backyards. Of course there's a technical distinction between the two which is important to the engineers who work in the field, but when a reporter or community complains about fracking they are complaining about the drilling, fracking, byproduct, and consequences that all arise when a well is created to take advantage of fracking.
> We are not just pumping massive amounts of harmful chemicals into the earth. Fracturing fluid is generally made up of 98 percent water. The other 2 percent is chemicals ranging anywhere from acid to anti-bacterial agents (used in disinfectants), to gelling agents (used in ice cream), to friction reducers (used in cosmetics), to surfactants (used in laundry detergents).... We are pumping very small amounts of them thousands of feet below the surface and then recovering most of them when the well is flowed back.
First, if you introduce enough toxic chemicals into an aquifer to contaminate the water, no one cares whether those toxic chemicals were initially introduced as a 2% solution, 20% solution, or 0.02% solution. Second, I'm pretty sure it's not the fracking chemicals that are coming out of people's plumbing and burning spectacularly when they hold a match to the faucet, it's the extracted gas. And if fracking is causing gas and flowback from the shale to be introduced into the aquifer then that's a huge problem, regardless of the other chemicals involved.
> Hydraulic fracturing is not contaminating drinking water. These fractures are being created about 6,000 feet below the surface.... If anything is going to risk the integrity of the drinking water, point the figure at the construction of the well, the steel and concrete barrier that is built to isolate that aquifer from a flowing well.
> I fully realize that this does not exonerate the oil and gas industry, but hydraulic fracturing is the one getting all the blame for no reason, and by people who clearly need to take a physics class.
And this is the author's main point. She's not denying that the oil and gas industry is contaminating drinking water and destroying communities. She's just arguing that it's the well-builders who are screwing up, not the folks pumping in the contaminants and extracting the gas.
I'm sure the this distinction is very important to the author. She is an engineer who has done hydraulic fracturing for the world's largest oilfield service company for 10 years. She probably believes the technology is great.
But if hydraulic fracturing brings new wells to town, those wells fail, and the flowback from that fracking process ends up in the drinking water and destroys communities then no one cares about which engineer is to blame within the oilfield company. It's still the oilfield company's fault.
Edit: Tweaked some of the terms I may have been using inaccurately.
And you're assuming that there is still a large supply of potential antibiotics waiting to be discovered and which can be discovered relatively quickly. Our current batch of antibiotics already attack bacteria in very different ways. How many new classes can we invent which are effective against bacteria but non-toxic to humans?
* 37signals believes that empowering employees to work remotely is a good thing (see Remote[1] and We Work Remotely[2]).
* 37signals also believes that a live/work balance is important and it's critically important to confine work to work hours whenever possible (see Rework[3] and various blog posts[4,5]).
* The problem with the Office365 campaign is that it sells remote access to managers with the promise that they can increase productivity by expecting their employees to work from dawn to dusk, and even while in the bathroom or eating meals.
Remote work and employee availability are orthogonal concepts. While remote work may enable more flexible work hours, granting remote access to employees should not come with the expectation that they are available 24/7.
I'm surprised that more people cannot grok this distinction, and if that's true here at HN then I really worry that Microsoft's Office365 campaign may turn out to be prescient.
[1] https://37signals.com/remote/
[2] https://weworkremotely.com
[3] http://37signals.com/rework/
[4] https://37signals.com/svn/posts/3180-a-good-days-work
[5] http://37signals.com/svn/posts/902-fire-the-workaholics
Edit: Fixed grammar issue. Added references.
The reason 37signals is going after Microsoft is because that dystopian future is exactly what Microsoft is promoting.
As remote work becomes more mainstream it's important for the proponents of remote work to emphasize to press/clients/employers/colleagues that remote access ≠ 24/7 availability and live/work balance is still important.
Where does David say this, and why do we consistently upvote arguments to the extreme at HN?
DHH is simply saying that encouraging people to work during their free time is a bad thing, and remote access doesn't magically make it okay.
Since you offered an example, let me give you another. I have a good friend who came down with the flu early last week (not "flu" as in cold, but the full-fledged flu). All she wanted to do was rest, but because she can work from home her boss insisted she pull 10 hour days while in bed with a fever. They would never have wanted her in the office in that condition, but somehow remote work made it okay. She's still not healthy and hoping to sleep through the weekend to recover.
I believe all the socket types except REQ and REP do have incoming/outgoing queues. There's just no requirement for a broker to serve as an independent queue.
Plus, keep in mind that most startups fail - this isn't like fire insurance. If anything, a consultancy like this might make it easier for founders to walk away sooner and with less guilt knowing that someone else will bail out their customers.
Also, if it's too expensive to do for everyone, you can of course offer it as a premium feature or a differentiator for an enterprise pricing tier.
Your agreement is great in spirit, but I believe the moment your company ceases to exist your customers will lose legal recourse over your commitments. IANAL, but I would assume that includes this open source guarantee. That's why there are a number of third party companies who provide escrow services. Iron Mountain is an example:
http://www.ironmountain.com/Services/Technology-Escrow-Servi...
Edit: Fixed formatting, wording.
The product/fit questions have already been asked, but there's still this: Why is Coin taking pre-orders several months in advance just to raise $50k? I can't help but wonder why a YC company wouldn't just raise the needed $50k from investors?
If this is an attempt to test the market, are you sure that a crowdfunding approach is the best image for a financial company? I want any company dealing with my financial data to be rock solid and reliable, and crowdfunding is the exact opposite of that.
Also, why aren't you collecting shipping addresses? I read your answer in the FAQ, but that makes me twice as concerned. You say, "A lot can happen between now and Summer 2014. For example, you could move. To reduce confusion, we’ll get those details from you once we get a little closer to getting you your Coin."
This is a problem for two reasons: (1) you are emphasizing that the ship date is far in the future, and (2) it comes across as though Coin is run by young founders who move around a lot and don't see value in long term planning. That's the wrong mindset for a company handling financial data.
Instead, Apple provided two alternatives:
* A vendor-specific identifier that is shared among all apps created with the same vendor prefix (essentially, coming from the same company). This provides what most devs need for identifying users within their apps and even across apps.
* An advertising identifier that is shared across all apps. This is intended for tracking, but Apple also provides a couple privacy protections for users: (a) users can set a flag asking apps not to perform tracking with this identifier, and (b) users can reset this identifier whenever they want –- the equivalent to clearing cookies.
Back in Lion, the Mac would began suspending/killing processes in the background:
http://arstechnica.com/apple/2011/07/mac-os-x-10-7/8/#proces...
Devs and ubergeeks got upset ("Steve Jobs is taking away control of our desktop too!"), but obviously we are seeing the benefits with battery life. And Mavericks goes much further:
http://arstechnica.com/apple/2013/06/how-os-x-mavericks-work...
Update: If there's any doubt how seriously Apple takes battery life, note that their WWDC 2013 talk/video on "Maximizing Battery Life on OS X" was given by Bud Tribble.
And what if the purpose is the absurdity of its monetary value?
I don't believe that Banksy's goal is to have his work be seen as curios. It's getting us to have these conversations.
Now there are many more Objective C developers, which has also led to rapid improvements in the language and a blossoming of third party frameworks.
Do you have evidence to back that up? I can think of a number of examples to the contrary offhand: The French Revolution was preceded by a financial crisis and poverty, as was the rise of the Nazism in Germany. There's Mohamed Bouazizi, the poor and repressed fruit vendor who helped launch the Arab Spring in Tunisia. And even the Occupy and Tea Party movements that have each arisen in response to the economic situation within the US.
Also, I believe an SQL-based approach is more appropriate for the smaller screen sizes with iOS. The master-detail approach on iOS typically works out to showing a master list with a few labels describing each object, then drilling into to the object's details. In many cases all the labels on a master list (plus an associated object id) can fit into a single in-memory array, and an SQLite query works great to pull these labels strings off disk when the view loads. There's little reason to have CoreData manage faulting/loading entire data objects as users scroll up and down the master list just to view the titles. Of course the SQL data access should still be abstracted, but CoreData is overkill in cases like this.
There are a couple other big fundamental differences with how Word supports styles:
1. Copy/paste behavior. If you copy formatted text into a Word document, it brings the styles with it. If you pull a lot of styled content into your document (including HTML), you must constantly work to restyle the imported content. FrameMaker (IIRC) helps you remap the pasted text to existing document styles.
2. Character styles in Word have always seemed like neglected step-children relative to paragraph styles. Both FrameMaker and Pages treat character styles as full peers of paragraph styles and give them separate picker lists.