adamsmith

Hi there!

We've done two things to address the sidebar motion issue:

1) We've improved the sidebar's motion with an updated layout that creates fewer visual changes, and

2) We've been building deeper integration into the editors, with new UX around completions and looking things up.

Check out the new demo video on the homepage—we think you'll like it! : )

Regarding datasec, unfortunately we haven't gotten to that level of security certifications yet, but we hope to get there soon!

Adam from Kite here. Thanks for all the feedback and encouragement around the launch today. We're excited to be opening up Kite for everyone to download today.

When we launched Kite here on hackernews almost a year ago we were blown away by the enthusiasm for our smart copilot vision. Over 65,000 of you signed up for Kite in the first 72 hours, and over the past year we've been working with many of you to deliver that vision. It's taken a momentous effort, but today we're ready to take off the wrapping paper and open up Kite to the world.

Here's what we've been working on:

* Deep editor integrations: to make Kite better for smaller screens and more integrated into the coding workflow. You no longer have to dedicate a sidebar of your screen to Kite; instead, recommendations from Kite replace your editor’s autocompletions and hover results.

* Fine-grained privacy controls modeled after the .gitignore file format means that you can selectively and precisely decide which files and folders Kite indexes.

* Next generation type inference engine that uses both static analysis and statistical inference over Github. Kite beats PyCharm and Jedi by 32% on a typical Django project, offering more completions when you need them.

* Ranked completions which put the most relevant completions at the top of the autocomplete box using techniques traditionally used in web search.

* Kite for Windows. (And Linux in testing!)

Check it out at kite.com.

We agree; these features are at the top of our list. : )

This is great feedback, and definitely something we need to address.

Initially we've been focused on giving users control and transparency. We need to extend this to employers.

One quick idea that we'd love your feedback on: a .kiteignore file that can exclude Kite from responding to files that match a certain pattern (e.g. "secrets.py"). Presumably an employer could put a "[^.]*" in a repo-level .kiteignore file, and anyone working with that repo would have to explicitly delete that file to use Kite with it.

We'd love to hear any other ideas folks might have as well!

The initial idea came from thinking about live contextual search and community. This thinking intersected with programming because of my background, and once that happened there was a lot of iteration—informed by research, and mostly conversations with friends—to get where we are today.

We want you to be able to use it just as much! : )

There will be an adoption curve from early -> late adopters. Working through this is something we're committed to, and we know it will take time.

We're committed because we think it will be incredibly valuable to our field. We just can't imagine a future 50 years from now where programmers don't benefit from a smart backend helping them work.

So we start with step one today, and here we go : )

We have some folks outside of the company using Kite already, and will be scaling that up as quickly as we can!

Supporting the variety of dev setups will definitely be one of our challenges. We've tried to start addressing this with 2 column mode (not shown in the demo video, but happens when Kite is in landscape mode; good for multimon), snapping to the side of your screen, and left/right-handed orientations.

This will be a long term effort. We have a lot more work to do here, along the lines of assisting with Z-index management, attaching to windows, etc.

Overall there's a lot to do! We will get there and are signed up for the long term.

We will begin inviting folks today. We want to control the upramp for two reasons: first, with desktop software, every time you take a step up in user base order-of-magnitude (1 -> 10 -> 100 ...) you see new bugs from odd desktop configurations. For example, we've already had one user whose machine wouldn't resolve "localhost" when docker was running : )

Second, we have to also manage backend scaling. We have some pretty strong systems engineers, but maybe because they're experienced they know what they don't know!

But we want everyone to be using it ASAP also.

RE open source, today we open sourced our client plugins (http://github.com/kiteco/plugins), and published instructions for writing your own. If you use an editor that isn't supported, it's about a 2-3 day project to create a plugin for a new editor. : )

I started slinging code in Visual Basic 5 back in the day, and ran Windows until recently. I hope to be able to jump into building the Windows client soon : )

Fortunately all of our UI is html and javascript, so no windows controls needed : )

Hi everyone, we couldn't be more excited to tell you about Kite and get your feedback!

We think connecting programming environments to a smart backend will improve programming in a lot of ways, and this is just the first step. We'd love to hear your thoughts on where we should go from here!

I thought this was going to be a reverse-MD5 on their gravatar url. Interesting to know this is there, too!

(As a possible improvement you could also take all possible matches and compare their MD5's to the gravatar URL.)

Cool! Thanks!

This is a really cool comment. Is there anywhere I can read more about the UI innovations Chrome took from Opera (or web browser UI innovations in general)?

1Password is a great example of an application doing this well -- when there are conflicts, 1Password detects this, and there is an application-specific workflow that helps the user resolve the conflicts. It's pretty slick.

With the advent of Deep Belief Nets, which can learn from lots of unlabeled data, it seems reasonable to believe you could duplicate or exceed the human ability to quickly understand a player's behavior based on past humans played.

If only we had access to the backend histories of an online poker site!

Facebook also has many more features, which probably means more code, which probably means larger switching costs. Take anything: photos, privacy logic, news feed, etc., and Facebook has the more sophisticated feature set.

You highlight really good points. I guess at scale the government does exactly what you propose (step in and allocate supply per person), for example rationing in World War 2.

In a disaster situation if there is no elasticity between price and supply then price gouging laws (social or legal) make a lot of sense. For example, if there's a fixed amount of water around regardless of price people shouldn't be able to raise prices.

But in this case there IS elasticity between price and supply, right? Uber is claiming that they'll deliver better service by increasing prices, because supply will increase proportionally. Thus, a functioning economy.

AND Uber is waiving 100% of their fees! Price gouging? Really?

(Side note: NYC would have more capacity for handing this emergency had they not given an artificial monopoly to cab companies over the last century, vis-a-vis medallions. I realize we can't change the past. Let's just be aware of it so we can learn how to improve.)

Cars will become more appealing than public transportation over time. As the downsides of cars fall away, their packet switched functionality will ultimately win out, particularly for wealthier people.

You are of course absolutely right! There was a bug (now fixed) that was causing only one cpu to show up in the VMs. All instances started after now should have the proper number of cpus visible.

(Note, the number of cpus might be higher than the number of physical cpus if the host cpu supports hyperthreading.)

How embarrassing (but fixed now). That was introduced when I added the ability to boot five instances without a credit card. Thanks for letting me know!

Yes, though I suppose you could just create another account. : )

You can stop a running instance by shutting down the OS. If it's something people really want we can add an API/UI mechanism to do it.

Ok!, the two instances you were seeing were duplicate listings of the same instance. That bug was introduced a few days ago by some database optimizations, and is now fixed! Thanks for reporting it.

The 1.56 core-hours is mostly from inst_KGN6tZdFgoeL2C9KPKBsNA which has four physical cpus and has been running for almost an hour at this point.

Thanks so much for trying this out!!!

That sounds like a bug! Just sent you email : )

Yeah, to be honest we're trying to avoid the business of selling wholesale access to a lot of IP addresses, hence the proxying of traffic.

If there are specific, legitimate uses for a large number of IPs, for example fighting DDOS, then that might be something we should build!

There's a surprising behavioral economics result that says people will do things for free that they won't do for small amounts of money. A check in the mail for a dollar or two every month isn't as compelling as being part of a group effort.

And empirically, it seems to be working. The number of contributing machines is currently in the six figures. The main risk right now is on the demand side, i.e. whether or not people want this type of compute.

If the 150 TB's slowed down local law enforcement enough to make them mishandle the warrant, any bets on how many petabytes he'll have waiting for them next time? : )

Why use cosine to interpolate v.s. a linear smear?

Got it. Thanks!