AI-Powered JavaScript Completions

Post by aerovistae » Tue, May 12, 2020, 7:45 PM UTC

zomglings wrote: post #51

aerovistae wrote: post #40

Semi-related thought~ I find myself often dreaming about the AI-assisted development processes of the future. I'll frequently be writing code and start thinking "this task I'm doing is pretty formulaic and constrained-- it should be automatable someday, even if we haven't figured out how yet." Examples: 1. I memoized the arguments for a util function. Repeat this on the very similar functions defined alongside it. 2.…

When is it better to solve those problems through the organization of your code rather than an autocomplete feature? The things you mentioned all seem to yield to the decorator pattern. Creating the right abstraction (instead of using autocomplete) would benefit future collaborators who may not have access to the same autocomplete functionality.

Post by jordache » Tue, May 12, 2020, 7:59 PM UTC

aerovistae wrote: post #40

Semi-related thought~ I find myself often dreaming about the AI-assisted development processes of the future. I'll frequently be writing code and start thinking "this task I'm doing is pretty formulaic and constrained-- it should be automatable someday, even if we haven't figured out how yet." Examples: 1. I memoized the arguments for a util function. Repeat this on the very similar functions defined alongside it. 2.…

Post by zomglings » Tue, May 12, 2020, 8:24 PM UTC

aerovistae wrote: post #71

zomglings wrote: post #51

Earlier quoted context omitted.

When is it better to solve those problems through the organization of your code rather than an autocomplete feature? The things you mentioned all seem to yield to the decorator pattern. Creating the right abstraction (instead of using autocomplete) would benefit future collaborators who may not have access to the same autocomplete functionality.

Even if that was true, which I'm not arguing one way or the other, it wouldn't take much effort of imagination to come up with other use cases that aren't solved by decorators. This has a taste of the old "they would have asked for a faster horse" argument.

Post by [deleted] » Tue, May 12, 2020, 8:36 PM UTC

adamsmith wrote: post #37

hasperdi wrote: post #21

FYI: Kite as a company had a backlash from the community after they acquired popular Python packages and injected their spyware and ads. So far they've learnt from that lesson, but who knows if they'll stay that way.

We hear you. We agree this was a mistake, and over the ~three years since then we've listened to the community, for example by releasing local processing for Kite.

Post by [deleted] » Tue, May 12, 2020, 9:11 PM UTC

nikisweeting wrote: post #60

adamsmith wrote: post #50

Earlier quoted context omitted.

Thanks for the thoughtful message! We hope you'll give Kite another shot. We're always improving it and have covered a lot of ground in the last few years. In particular, a common complaint about TabNine on Twitter is that it's heavyweight. Based on our comparisons of today's Kite versus today's TabNine, we believe Kite uses less CPU/battery, and far less memory. (My teammate dhung posted a longer comment about TabNi…

To clarify, my complaints about Kite being heavyweight are 90% about the UX flow being heavy, not the CPU/RAM usage. Kite seems to require a background daemon, Electron copilot app, and editor plugin, with a multi-step setup to customize what things are shown on hover vs ctrl+space vs tab. By comparison, Tab Nine was a single command to install in SublimeText, and I have never had to interact with it since other than…