incepted

Are you trying to kill me, Microsoft?

Right now, I'd say they are looking pretty good: they hacked into the phone of a terrorist without breaking any laws.

They just hacked into an iPhone, something Apple has been claiming for a long time was impossible. Even Apple has no clue how they did it.

Incompetent they are not.

You're looking at political theater, that's it. But there's little incompetence flying around.

How is it the FBI's fault that this particular iPhone was not secure?

It's mystifying to me how far Apple advocates will go to not blame their favorite company.

First, it's Apple sticking it to the FBI by making a stand for privacy and receiving public accolades doing so as a champion of privacy. The FBI is the bad guy trying to invade our privacy.

Now, it's the FBI sending a giant "screw you" to Apple by not only letting them know they were able to hack into the phone without Apple's help but at the same time, making a mockery of Apple's entire security claims. And now, Apple is in panic mode, slowly realizing that they went from being the hero of privacy in the modern age to the company that wasn't able to secure its phone from the FBI. From the FBI. Of all things.

No wonder they are freaking out and they want to know how the FBI did it.

Except that if I were them, I certainly wouldn't ask that publicly, I would at least pretend I know how the FBI did it and claim that it's already fixed in the next version of the OS.

Which still means that tens of millions of iPhones are at risk today and will be for months, but at least, you get to pretend that you're ahead of the FBI while right now, it's pretty obvious that Apple has been outsmarted by a government agency.

The bottom line is that in this line of work, it pays to be discreet and humble.

The value of an email service is how many users it has.

The value of a big database is... who knows? If Google one day decides the content of that database is a strategic asset, they might just as well decide to shut it down to the public and continue using it internally.

Still doesn't mean Google will maintain the public access to this database. They might just as well shut it down and limit its access to Googlers. Like they already did a few years ago.

What the organizers of that conference fail to see is that inviting someone with such a toxic and racist personality will only encourage that person to keep posting their hateful comments.

That same person was once invited at another conference (QCon I think?) but was then uninvited after the organizers of that conference were made aware of that person's posts.

You'd be surprised how many users have no idea whether they are running the 32bit or 64bit version of their OS. For them, running a Go binary will be anything but easy.

... as long as you downloaded the right binary.

If the wording bothers you, replace it with "We should only accept symbolic operators that are taught up to sixth grade".

I like the Litmus test that a ten year old should be able to read them, which means that +, *, / and - are fine but =~> and other nonsense should be banned.

With dynamically typed languages, you get cryptic (and vague) errors and auto completion just can't work.

Oh, no! Seconds? Like five? Seven? For a process that you start less than once a day? Unacceptable.

> High memory usage. Heaps in the 1-2 GB range are not uncommon.

So... what? Spend an additional $30 on your build server and add 8Gb to it. Problem solved.

> - XML configuration files.

XML is fine. As opposed to Groovy, IDE's do a great job at offering auto-completion on it. But if Groovy is your bag, you can use that too.

> - Non-Unixy feel.

I have no idea what that means and I've been using UNIX for about thirty years now.

I think the future belongs to statically typed languages that can offer DSL's as terse as Groovy but with actually types in them, so that the IDE can actually do the job it's being paid for.

It's never healthy to be so dependent on one provider.

Correct, there was no SDK on the first generation iPhone. It was a closed device, like all Apple devices. And that's how Jobs wanted it, he just thought that the idea of third party applications running on this device was pure absurdity.

Then Android came out and Jobs had to adapt.

> Apple made what turned out to be a really smart business decision: they released an iOS SDK and an App Store and the rest is history.

Kind of. Apple made a really smart business decision: they realized that if they didn't match Android and provide an SDK as well, they would lose. So they followed suit.

> The end result, for those of us still trying to build installable web apps for iOS was that with nearly every new iOS release some key feature that we were depending on broke.

This makes it sound as if these features got accidentally broken. No, they were intentionally removed or crippled because they either threatened Apple's dominance or cut into their profits. You could call that another set of "really smart business decisions"

All you need is learning how to prioritize your time. A lot of adults can do that.

So effectively, you prefer to use tools that give you less flexibility and that's why you prefer the iPhone.

He didn't mean to but this is the general reflection of the culture that permeates Apple as a company and the bubble in which they live.

I remember once one of my wealthy friends saying "I don't understand why people live in one bedroom apartments". I stared at her for a solid minute to determine if she was joking but no, she was dead serious. She genuinely did not understand. She was born and raised in a wealthy family and she just had lost track of the rest of the world.

Schiller and the Apple execs have similar blinders on and once in a while, the mask drops in a public speech because the speech writers and their proofreaders have similar blinders on and didn't realize the enormity of the implication.

You were asking for modules and now you're down to the function level. That's a much easier problem to solve. Hoogle, Javadoc, documentation and good index engines solve this problem easily.

Note that type only is pretty ambiguous and most of the time useless without additional metadata. Types tell you what, they don't tell you why or how.

> - When multiple modules are returned, similar packages, how do you compare and select efficiently without wasting hours reading the code, evaluating it, checking if it is still maintained and hoping there are no hidden bugs etc.

At some point, the human brain has to step in and make a call. You can't expect an automated tool to dictate to you the code you need to write.

I don't understand what part of this doesn't qualify as a "reusable module" to you.