Well, why don't we just test it for ourselves instead of wondering?
Let's see here: login to a site, open a new private browsing window (Chrome), load the site, am I logged in? Nope. Cookies from your normal browsing are not transmitted in private browsing mode.
Exactly. Square is trying to build up a collection of services to offer local businesses, especially restaurants, of which payments is just one. Google has been playing in the same game, with the main aim of selling ads to local small businesses, but hasn't really moved fast enough in pushing payments.
Do you honestly think that poorer people are poorer because they sit around watching Breaking Bad all day? Have you perhaps ever met someone who works hard at three jobs at minimum wage and can't make ends meet, especially in an incredibly expensive city like NYC? I mean what planet are you living on?
And we don't necessarily have to take every single view seriously. The vast majority of people don't want a massive polluting factory built next to their single-family home. The fact that a few people disagree doesn't mean that every project get bogged down in a discussion of the legitimacy of zoning as a concept.
I can't find the specific Photoshop compatibility issue you're thinking of, but there are numerous similar stories in the archives of The Old New Thing that might be of interest. He's very much still writing.
Publicly traded stocks are subject to a large number of regulations that have the intent to protect investors. The point isn't to make it impossible to lose all your money; the law will gladly let you give it all away if you so choose. But the idea is that people should have the necessary information to know what they are getting into. In exchange for exemption from SEC registration requirements (which are costly for a small company to deal with) and less disclosure, companies can only deal with accredited investors.
Because of literally hundreds of years of investment scams that bilk people out of their life savings. Publicly traded companies are subject to various securities regulations that require disclosure of certain pertinent information and protect investors in various ways. Smaller companies can be exempt from many of these regulations (which is a useful thing, as it costs money to comply), but in exchange, they don't get to ask every random person they encounter on the street for investments. The alternative isn't to lift all the restrictions; rather, it is to impose the same regulations on companies big and small alike, which would be particularly harmful to small businesses.
Call it a nanny state restricting your liberty if you'd like (though realistically, there's little enforcement of the investor accreditation rules), but since it's the same nanny state that is supposed to keep you from being destitute if things don't work out, we're going to impose some restrictions to keep the worst abuses from happening first.
There's an EFF fair use test case involving a YouTube takedown of a toddler bouncing around to a 29 second clip of a Prince song playing in the background: Lenz v. Universal. It was filed in 2007 and has yet to be resolved.
The fact is that while section 512(f) of the DMCA provides consequences to misrepresentations by those making takedown requests, it is damned impossible to actually enforce that.
Yeah the FAA isn't going to buy the use of Flytenow as an intermediary. And surely people are going to be offering flights they weren't going to be taking anyway.
Because competition in the browser market is vital to keep the web platform progressing and to prevent a single party from controlling web standards. Do you remember the dark ages when IE ruled the web and things like HTML5, canvas, webgl, etc... couldn't happen?
This actually isn't a joke? I got to the point where it asks for a credit card number, seriously expecting (hoping maybe?) for a "Haha!" message, and yet...
Two reasons. The first is that these people often don't look like salesmen. They come in appearing to be providing impartial advice, and all the incentives, commissions, etc... that bias their advice are kept secret. The other problem is that these guys are often pushing complex products to an uneducated public where small details can make a big difference. A small change in an annual fee for an investment can, thanks to the magic of compound interest, easily add up to huge differences in investment returns.
This may be the most baffling thing I've ever seen. Why? Imagine if they put this kind of effort into solving, I don't know, virtually any other problem in the universe.
I don't see why they wouldn't be willing to talk to the legal department of, say, GM and clarify the exact terms for a license. The blog post is a general statement of intent and the lawyers can discuss specific details as they apply to particular situations.
Elevators. I mean obviously there are significant structural concerns as well, but elevators are a big part of what makes building super-tall buildings uneconomic and impractical. The Elevator Conundrum, as Wikipedia dubs it (https://en.wikipedia.org/wiki/Skyscraper_design_and_construc...), means that as you build a taller building, you need more elevators to service the floors. More elevators take up more space, meaning less rentable space for occupants. While skylobbies, double-deck elevators, and other tricks can help, they don't eliminate the problem, especially since no one is willing to transfer elevators four times to get up/down. We also run into the issue of how to build a 10,000 foot elevator, which is so far outside the competence of manufacturers that it would represent a huge risk to the completion of the entire building project.
I am, of course, assuming you plan to build a useful tall building instead of an empty 10,000 foot tall shell for no particular reason.
More specifically, there's the iOS 7.1 to 8.0 API Diffs: https://developer.apple.com/library/prerelease/ios/releaseno.... Note that a huge number of the changes are just small changes to argument lists (there are a gazillion of these in Accelerate, filling the top chunk of the diff doc) and a number of other change come from the switch from (id) return types to (instancetype) in init: methods. Also, getter and setter methods have been replaced with properties in many classes, which doesn't break any existing code, but generates changes in the API diffs.
CNN really screwed up this story (and issued a correction). Amazon Payments isn't remotely new; most of this stuff has been around 6+ years. The only new thing is better support for reoccurring subscription payments. A nice new feature, but the whole project is nothing new.