AI.JSX (https://github.com/fixie-ai/ai-jsx) is a framework specific to AI App development, but it's built to integrate with React / JS UI development.

So I think the answer to your question is "both". :) To build an AI app, you need many of the same skills you need to build any other type of app. But it's not like AI is some spooky thing that only ML pros can touch. It's accessible to any dev.

Nothing about this forces any government projects to do anything. It's just recommended guidelines.

Maybe the title should reflect that?

I am excited to look into gulp!

Yes, I acknowledge in the article that Grunt is not designed for this, and if you use Grunt for what it is designed for, it works pretty well. However, it wasn't obvious to me the using Grunt to build an SDK was outside of its scope when I started the project, so I figured it may not be obvious to other people as well.

Although Stalin's USSR didn't technically believe in a deity, it still has many religious elements:

* Violently throwing out competing religions, like Christianity

* Belief in a single god-king (Stalin)

* Total faith in the power of communism as the most perfect solution to the world's problems

* Harsh punishments handed out to those who question the orthodoxy (gulags)

* Obsessed with submission of the individual before an institution

Blind, violent faith in bad ideas could reasonably be blamed for a vast amount of the world's problems.

s/faith/{dedication, ferver}; and even if faith is an acceptable term there, faith != religion.

Again: same bug, different exploit.

passion?

Something like that. Look carefully at the roots of the word "passion." It involves suffering and sacrifice.

maybe not "passion" per se, but the bug is people's willingness to believe things on insufficient evidence because it gives them a sense of purpose or binds them to a bigger group.

Yes, it certainly wasn't created to spite Steve Jobs, because Metro shipped with Windows Phones in November 2010, just under a year before he died.

My main problem is that it has awful support for functional programming, which I find to be a really helpful way of doing something like a web crawler, where you're essentially describing a computation to parse some input. I would use F#, because it offers powerful functional programming tools, is on .NET / VS 2012 (not sure if that's a pro or con for you), and has type inference (so you get the benefits of static typing without the cost of writing out the types of everything).

You should probably check existing web crawler solutions to see if you can adapt them before rolling your own.

I was wondering about that. It's the same at the end of the Surface video.