by csmajorfive on 5/12/20, 3:00 PM with 94 comments
by hasperdi on 5/12/20, 3:45 PM
by adamsmith on 5/12/20, 3:10 PM
After years of work building our Python product — now to over 250,000 monthly active users — we decided we were ready to expand a new language. JavaScript was a clear choice given how well it pairs with Python, and it was the our most-requested language.
We took what we learned from building our Python product, adjusted it to JavaScript’s nuances, and trained the model on 22 million open-source JavaScript files. We then spent months dogfooding, user testing, and applying advanced model filtering techniques to ensure the UX was ready for everyone to enjoy.
We think the end-result will help you have more fun writing JavaScript, while also helping you ship software faster. We can’t wait to get feedback from you to help us improve our JavaScript completions from here! We'll be online to answer your questions here today as well.
Since a lot of folks ask, Kite continues to work 100% locally and Kite for JavaScript is free. We plan to release support for more languages later this year, and are taking requests at kite.com/letmeknow. Thanks!
by aerovistae on 5/12/20, 4:44 PM
Examples:
1. I memoized the arguments for a util function. Repeat this on the very similar functions defined alongside it.
2. I need to put a wrapper component around six similar components. Just do it for me after seeing me do it once.
3. I imported a new logging mechanism and called a specific method from it in one of my class's methods. Repeat for four similar classes.
Basically I want a "repeat after me" functionality that can intelligently infer which part of thing I just did is generic and can thus be replaced with the next item in the series. In a dream future it would also infer what the next items in the series are.
I haven't a clue how such a thing could be created though, or I would already be on it myself. It would have to understand the code not just syntactically but conceptually.
God it would make development less tedious though. The difference between today and that future is the same as the difference between today and the days of punchcards.
by r29vzg2 on 5/12/20, 3:11 PM
by rickstergg on 5/12/20, 4:05 PM
by douglaswlance on 5/12/20, 4:30 PM
by thway554897256 on 5/12/20, 3:48 PM
by vj44 on 5/12/20, 7:05 PM
by enitihas on 5/12/20, 3:26 PM
by mosselman on 5/12/20, 7:03 PM
Sure if you are just re-implementing the same thing over and over, then this might come in handy, but so would using OOP.
Again, haven't tried, just some thoughts.
by chris_engel on 5/12/20, 3:18 PM
And it costs more than my whole IDE (IntelliJ complete license for _everything_) as well...
by darkbatman on 5/12/20, 3:43 PM
by forkLding on 5/12/20, 4:02 PM
by weareconvo on 5/12/20, 11:02 PM
by aaronpaz on 5/12/20, 7:06 PM
by brauzi on 5/13/20, 5:12 PM
by kvothe_ on 5/12/20, 6:09 PM
by viva95 on 5/12/20, 4:08 PM
by tobr on 5/12/20, 3:38 PM
by nikisweeting on 5/12/20, 6:09 PM
The thing that convinced me in the end was that Kite had a super heavy editor integration UX that needing a constantly-running Electron "copilot" app, even uploading some of my code without clearly asking for consent first. This has maybe changed now, but at the time that was my impression.
Meanwhile, TabNine has almost no UI, it's just the tab button and nothing else, and somehow the autocomplete "just worked" amazingly well with any language I wrote, including English prose. The ratio of "fuss" to "gain" was just so different between the two. One I barely remembered I had even installed anything, my editor just suddenly became a pair programmer overnight, and the other felt like I was running a whole electron app just to get occasional library headers autocompleted and docstrings on hover (in only a few supported languages).
I wish the Kite team all the best though, and I hope to see their solution grow and improve. There is definitely room for more players in this space, and I know they've learned many lessons from their past issues with code uploading UX, so I hope people give them a break over that past PR gaffe.
by sync on 5/12/20, 3:34 PM
by hartator on 5/12/20, 9:18 PM
by brenden2 on 5/12/20, 3:08 PM