They have enough money to give building the first ever BFR a shot. If it turns out good and the reusability works, they can do a lot of contracts with it, like servicing ISS, and launching a new big space telescope. From there on the advantages and possibilities of having a reusable high payload system will be very clear, and with 3-4 of them, a moon base would already be possible. We'll see what happens but the plan looks solid at least.
I think what he is trying to say is, that developers will be useless dead weight in this kind of post apocalyptic scenario. Everybody will be out of there normal day jobs, but a lot of people can contribute to survival with their skillset.
Doctors, mechanics, farmers, caretakers, hand labor, etc. will be in high demand. Office people & developers, not so much.
Am I one of the rare developers that grew up in rural USA that has remnants of what are now known as survival skills but I just consider as childhood fun?
I always tell my team that if things go bad then I'll be the one keeping them alive.
We are not dependent upon any specific technology. We are "fixers", and computers are just our hammer that makes everything else look like a nail. Take them away, and the other, lesser tools in the toolbox are still there.
I intend to attach myself to a raider strongman, to provide solutions to their difficult problems, such as how to crack an entrenched survivalist's defenses and get his stockpile out. I'm a decent hand at basic chemistry, too, like organic extractions and distillations.
There are many potential princes, and Machiavelli only needs one of them.
A bit sensational to call a reference to an unknown product that's likely going to be unveiled in 2 days, as well as some minor feature like Animojis, a major leak. This is what suffering a major leak looks like: http://gizmodo.com/5520164/this-is-apples-next-iphone
I'd argue that this is even worse than the misplaced prototype. This leak confirms much of the speculation around the design of the new phone but also gives away new information about the software it will use (animojis, faceID) plus the new Apple Watch with LTE.
I disagree. We now know what FaceID is called, how it works, exactly what the device looks like and how the status bar works, that there are new AirPods coming, the name of the new thing, the name of the updates to the old thing, and a software feature that no one could've ever gotten out of hardware chain leaks.
This is without a doubt the biggest leak since the iPhone 4 you pointed too. If it wasn't for the HomePod firmware leak a month ago this would've been even more devastating.
"Devastating" is an awfully strong word for what's happened. Really curious people know a few features a little earlier than they would have otherwise. It's hard to prove that this will even have any negative effects; it generates buzz and excitement around a launch.
For a personal anecdote, I honestly didn't know there was a new iPhone coming out soon. Now I do, and I'm curious. Plus, my sister-in-law mentioned this morning that she wants a new phone, this might help her decide. I don't understand why this is such a terrible thing.
Negative affects? No, not really. But Apple managed to have a TON of secrecy this year where no one was really sure what was going on. We didn't even have much in the way of hardware leaks this year.
Then they had the HomePod leak, now this. A lot of the surprises that we're going to be in their presentation are now known by the enthusiast set.
It's really a stolen thunder/pride thing.
I'm a little surprised you didn't know a new iPhone was coming as they announce them the same time every year.
Let me ask you this: everyone was going to be talking about it on Tuesday anyway. In what way would Apple benefit from having this news released two or three days early?
If a competitor put out a bunch of news on Friday then this would be taking up their PR time so there could be a benefit, but as far as I'm aware that didn't happen.
There isn't really anything in here that will help people get used to some possible controversy (like the leaks of the lack of the headphone jack on the seven).
What would this accomplished other than to make the Tuesday event less special/magical?
> everyone was going to be talking about it on Tuesday anyway
I imagine I'll see a headline in the news on Tuesday, probably a HN thread, and maybe a 30% chance someone at work will mention that there's a new iphone coming out. The 10 minutes I spent reading this article are a fairly significant increase in total attention I'll give to the release.
I agree, but I don't think this raises the hype over what we would've had after Tuesday anyway. If anything I think it slightly weakens what would have come from Tuesday.
It's not like there's only the One Big Leak that can be called major. This is pretty damn big. Now the whole damn world know what the next iPhone looks like, what features it will have, and then some.
Apple does leak things intentionally, we pretty much know that. For example last year it's widely assumed that they were responsible for the leaks about the headphone jack disappearing so that the enthusiasts set would know what was coming and have some time to "get over it" some.
It's also assumed that Apple leaked the thousand dollar price for the original iPad just so they could announce it at $500 and blow everyone away.
In both cases the leak benefited Apple.
I'm not sure what in this leak would be beneficial to Apple. All it does is make it so people will be less surprised on Tuesday and they won't be able to catch people by surprise as much.
I'm strongly willing to bet that this leak (in the HomePod a month ago) we're purposefully done by Apple.
It's pretty obvious someone did this purposefully, but I don't think they did it with Apple's blessing/planning. It was an individual employee (or a few) doing it on their own.
Would you say they suffered? It would be interesting to know which leaks are sanctioned, as well. This one? It looks like it just gives them more free publicity.
Anything about Apple gets publicity, but now it's not as much of a surprise on Tuesday. They work really hard on that surprise so I don't see why they would leak it Friday.
Sometimes the leaks have a clear benefits to Apple, I don't think this is one of them.
I'm going to speculate that anyone who was interested in Tuesday's revelations will still be observing on Tuesday. This is Apple, after all. They have a pretty dedicated following.
Before the GM leak, we had no idea how the status bar and face recognition would operate. Now we know all of it.
Unless Apple has other hardware in the pipeline or another hardware feature for the TV or Watch, there will be no surprises. I'm sure the execs are pissed, as they want people to watch the keynote completely unspoiled.
What was the nature of MTV? For me it was insatiable desire. Thats the very nature of Americans. We want what we don't have. One of the characteristics of American consumers in the early 80's was Shop till you drop. "I want it. I don't know what it is but I want it." - Dale Pon, Advertising exec part of the MTV launch campaign in Aug 1981
OSX is still pretty great. After Snow Leopard, for a while it looked like OSX is gonna turn into "iOS Desktop Edition", starting with Lion. But that never really happened, Sierra is a very nice OS, and High Sierra is basically the same thing with the OS using Metal.
(Now if only Apple would sell a Macbook or iMac with 512 SSD & 16 GB RAM for a reasonable price)
Wikipedia[1] reports deficit was ~1,250 bilions in the 2011-12 timeframe, dropping significantly in 2013. Wayback machine[2] seems to indicate the author wrote the page in the 2013 timeframe, so the figures probably need updating.
It's not that bad. The only thing Google/FB/Twitter gets to know is that a user Y is using app X. Nothing more, and not detailed usage stats, just the basic fact.
For that they handle the complete user registration, recovery & auth process for you, with all the work and pain attached to it.
Granted if your OAuth provider were really evil, they could log into the users App X account and access whatever data he has inside the app, so you have decide if that a concern or not.
Yes, but they get "only" that, but with it, they get, time/date of when you use the app(and perhaps how long, depending on how you/they handle logouts). Plus they get this for EVERY app that's used. You start aggregating this information and suddenly you can tell a LOT about a person. Plus this is all for ad dollars, FB/Google/etc can(will/do?) sell this information, to anyone willing to pay for it.
For a hello world app, no big. For a game app, what happens when your employer buys the data, and notices you are playing games on "company" time... Of course lots more privacy failures can be easily imagined here. I picked low privacy failures, but larger failures are very easy to imagine.. Especially when we know that most large governments also have this data, directly siphoned from Google/FB/etc.
Good links, thanks. At WWDC Apple was saying that Chinese, Japanese & Korean localisations for iOS Apps are often overlooked, and their data shows they should be the first ones to be added after English, even before localising for the more traditional languages.
I was looking into getting my app translated, but haven't even thought about OAuth providers.
I wouldn't say that QQ is dead, I have definitely seen people use it on their laptops in class at uni. A number of classes also used QQ groups for announcements, Q&A, etc.
I agree that WeChat is more popular, though. Those who have both my QQ and WeChat contacts overwhelmingly go though WeChat.
I've seen tons of people using iPod touches as dev devices. Much cheaper having multiple iPod touches running older iOS, or iOS betas, then having that many iPhones.
Show me your flowcharts and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won’t usually need your flowcharts; they’ll be obvious. Brooks
I agree. I use spaces and 2 to 4 depending on typical language style but even then heavy nesting is obvious.
I have a project full of essentially 'if (true) return true; else return false;'. Sometimes heavily nested. It's just not necessary.
Guard-style returns go a long way but a long column of those may mask deeper problems of structure. I don't mean inheritance-polymorphism no-ifs but rather your code isn't dumb enough and perhaps your data isn't smart enough.
