I was responding to this, specifically: "The laws in SF are as renter friendly as you can get in this country. I'm not sure what all the fuss is about."
If those tenant friendly laws are de facto easy to work around - and they are, particularly for poorer tenants - then they are significantly weaker than they seem. That's what the fuss is about. Poorer people get driven out because they don't have the time and money to fight their landlords trying to double their rent, whether legal or not. Richer people like me are able to fight it and win.
I don't think you understand California or San Francisco rental laws. They do not say you get to perpetually live in an apartment even if the owner doesn't want you there. They control how much a landlord can raise rent, and limit some forms of eviction. But they also have many exceptions, and the burden can be on the tenant to prove the landlord is wrong.
I'm a Googler living in SF, and my landlord recently tried to drive me out of my apartment, so I think I have an informed perspective on this.
It's not as simple as you make it out to be. The laws being renter friendly are helpful but they don't solve anything. If I hadn't had the time and money to try to fight this I would probably be looking for a new place right now.
Context is everything here. There may be a number of companies that fit the pattern, and she could be speaking hypothetically, but Rachel worked at Google and has an axe to grind.
He's joking. From the front page of warscapes.com: "What does the NSA make of James Joyce? The author finds out the hard way in his imagined brush with US intelligence over the PRISM data-mining program..."
That wouldn't solve or even sidestep any political issues. You've still got problems like:
* ip geocoding to decide which language to serve the UI in
* what do you call the languages? Chinese vs Traditional vs Simplified, or Farsi vs Parsi vs Persian, as mentioned elsewhere
And while political boundaries are messy, language boundaries are even more so. How do you decide dialect boundaries? And once you do, how do you decide which dialects get separate domains?
One of my coworkers had an off by one error when booking a return flight and overstayed his visa by a day (not in Singapore). So yes, it happens by accident. The idea that he should be caned as a result is ludicrous.
There are lots of data sources other than Street View, satellite and aerial imagery being big ones obviously, but also user provided data, Business Photos, phone calls, etc.
The Yellow Pages attribution you see doesn't necessarily mean all data came from Yellow Pages, just that some may have.
Maybe that typical system has a gender bias then :)
Perhaps if women are implicitly required to negotiate, and choose not to, then they will be recruited by another organization who is willing to pay them more without negotiation. You've just lost out on a good engineer - the employer has done themselves a disservice.
I used a functional-reactive-language-that-compiles-to-javascript for a web app, in a project that lasted about 3 years. It solved callback hell, and solved some UI problems, but created some hard UI problems as well. I'm not sure how this would translate to a server, but some examples anyway.
It seemed impossible to completely escape imperative programming. Mouse click handlers for example were much more natural to write imperatively; changes made in the imperative code would propagate as signals in a reactive way.
Reasoning about what happened around the boundaries of imperative and reactive code was hard, especially as the application grew in complexity. If I have a UI element that depends on two other signals - think spreadsheet cell with a formula that depends on two other calculations - do I want to update it as soon as one signal changes? do I wait for both to change? Do I want different behaviors in different circumstances? It often led excessive layout changes as values passed through intermediate states, or code being executed multiple times unnecessarily.
I assume you're referencing stevey's rant, and if so you're conflating two issues. Steve was talking about the use of APIs between services at the application level, not the API for the datacenter/cloud as a platform.
What reason would Google have to object anyway? Bigtable isn't open source so there's no benefit in shutting down work on Accumulo - the man-hours are not going to go into Bigtable instead.
It's significantly different from a patent trial. In this scheme the patent is not granted - and can't meaningfully affect the market - until it has passed some level of technical scrutiny by a (hopefully) neutral third party. In a trial the patent has already been granted, it's already affecting the work done by engineers, licensing fees may have been paid, and so on. And the evaluation by experts in the trial seems less likely to be neutral.
If those tenant friendly laws are de facto easy to work around - and they are, particularly for poorer tenants - then they are significantly weaker than they seem. That's what the fuss is about. Poorer people get driven out because they don't have the time and money to fight their landlords trying to double their rent, whether legal or not. Richer people like me are able to fight it and win.
I don't think you understand California or San Francisco rental laws. They do not say you get to perpetually live in an apartment even if the owner doesn't want you there. They control how much a landlord can raise rent, and limit some forms of eviction. But they also have many exceptions, and the burden can be on the tenant to prove the landlord is wrong.