adyus

Yes. Some are more successful than others.

Or https://canopy.co, among dozens of others.

Defining comfort is a whole 'nother beast altogether.

What's "comfortable" to a person choosing an SUV as their third car because they already have a convertible and sedan is entirely different to someone stuck on public transportation, for example, who'd appreciate anything with a running engine.

Are you playing with iOS 10's SFSpeechRecognizer & AVSpeechSynthesizer yet? Looking forward to Snips doing much more!

I'm using index document paths on S3 + CloudFront right now, it's definitely possible. Unfortunately, I don't remember exactly what I did to make it work. Some more Googling might give you the answer.

Edit: the setting is called "Default Root Object" when setting up a CloudFront distribution with an S3 origin.

"The problem is that being really smart is obscenely expensive" - or depends on luck in the genetic and family environment lotteries.

Perhaps because the large mass of consumers only care about the first point (how the hardware looks in their home)?

Point two comes in play only if the user experience is horrible, otherwise it's acceptable.

Regular consumers rarely think about point three.

I've worked on integrating Plaid into a project recently. Before getting access to the production version (more than 100 users), there's a pretty thorough security questionnaire (hopefully followed by some fact-checking on Plaid's part) for the client.

They are doing their best to weed out bad (or security-ignorant) actors, but there's only so much you can do with banks directly, like you mentioned.

Professional traders get paid to trade, not necessarily to win.

I'd assume push-button, since passive listening would drain the battery pretty fast.

Come to think of it, there's no battery-powered passive listening solution currently. Hmm...

Would you not be able to proxy that audio through Nuance and display text on the Pebbble screen?

To build on that idea, you could use PocketSphinx for (battery-draining) always-on listening for a keyword, then sending the actual recording to a server for transcribing.

Take a look at https://tensorflow.github.io/serving/serving_basic and https://tensorflow.github.io/serving/serving_advanced

Time is never free, even when it's free :) There's opportunity costs.

It doesn't seem to be (very) different. The blog post mentions Ruby's VCR library but not the node-equivalent https://github.com/carbonfive/nock-vcr or https://github.com/poetic/nock-vcr-recorder.

It's simply a new approach to a solved problem, it seems.

What about cherry-picking modules, briefly going through their source code (and, hopefully, test suite), then manually (read: copy/paste) importing them into the project at hand?

What are the ethical implications of this, though? Is it different than importing the module directly via package managers, license file and all?

I believe he may have meant "glue one together from parts found on Github".

Case in point: https://github.com/Shopify/dashing

If every employee quits their job to start a business, who will all these new businesses employ?

setTimeout() ?

I've been meaning to ask someone at Wit.ai this for a while:

Since your service is completely free, how do you plan on surviving? Would you open source any parts of Wit.ai should you go under?

I feel these are important questions to ask before investing time & energy into using your otherwise awesome service...

Clearbit could be one of the solutions to this.

I'd suggest focusing on getting something to work, regardless of what you write it in. Then, if time allows and if it gets traction, refactor it.

But the main focus should be to get something working.

Take a look at layer.com. Perhaps you could find something that sets you apart (low latency and lots of connections, plus a good price for Android devs, for example) and market to developers.

If you'd like to have these problems solved for you, give Meteor.js a try. Almost everything's reactive out of the box. It could be perfect for a small, realtime app like this.

You could always use the DDP library [1] ("REST for websockets") for realtime transfer. It's separate from the "core" Meteor package (a collection of packages, really).

There's also a list of libraries for other languages that communicate with Meteor via DDP. [2]

[1] https://www.meteor.com/ddp [2] http://meteorpedia.com/read/DDP_Clients

Could it be that "want" is now a type of currency? It seems that some of the things people "want" and get for free (GMail, Facebook, Twitter) have been converted to money somehow.

Give USERcycle a try.

Of course, it can't hurt to give them some competition. Just make sure there's enough demand, and that you're offering a strong enough reason to choose your solution over any of the others.

Hi Bogdan,

Without being mean, I don't believe this is the "missing" analytics tool. I can name three products that already cover all of the features on the landing page. You might need to dig deeper for a USP.

That being said, kudos for putting up a quick page to gauge demand. While I have my doubts about the results, you're going about it the right way :)

How do you feel about Meteor.js?

Excluding hermits, living anywhere is living within a tribe.

The largest tribe is currently that which accepts a commonly defined currency in exchange for providing value of some sort.