Regardless the author and I disagree strongly about the actual usefulness of Copilot. I do think ML could be a huge boon for many human applications, like coding, but it's far far from it. Furthermore Copilot's specific implementation seems to leave much to be desired.
To me ML is an infant right now and we're metaphorically and literally expecting that infant to drive a car. ML is in a weird, weird place.
Worse its not even a license forever, nor even for a period of time. It's priced by the word.
I would like some assistance.
I only ever pictured using it on open source stuff if it turned up decent
If folks are looking at this thing like "that's going right on my work PC" I would highly recommend reviewing your IT usage policy first. Yikes.
"Can't get into trouble if it's never published publicly"...which is wrong, obviously.
Edit: it may not be supported right now, but it is mentioned in the Goals section.
It took several seconds and added some logic I didn't ask for, but this is already interesting.
E.g., I set it to vue.js codebase. Then for each key I press it will:
1. create a new file if we're at the beginning
2. for each key pressed, output a character for that file
3. once the file has been "typed", close that one and open the next file and repeat.
4. once the whole enchilada has been "typed", then each key press will spell out "git commit..." on the command line then enter
5. once committed, each key pressed will spell out "git push..." then enter
6. etc. until I've typed the whole history of vue.js!
Maybe a "turbo mode" so I can set N characters for each character I type...
You know, there could be a kind of "bloat battle" game from this.
* player one tries to keep smashing the keyboard to "write" code and "commit" new features until the program can read email
* player two smashes keys to add low-effort issues to the tracker, post FUD to the mailing list to slow down the process, and add subtly wrong features for review on merge requests
Like hungry hippos except it translates directly to real world experience
Click on a file to bring up the diffs browser.
Disclaimer: I'm the creator of the tool that I'm linking to.
But thanks for the tip about Emacs undo tree, didn't know about that. With some add-ons you can apparently eg find undoable changes for only some region of a buffer, etc.
This is built into Emacs (no add-ons needed). Calling undo with a region selected undoes changes only in that region.
So, if you use GPT-3, it will not be finetuned further on code like Copilot, only pretrained on data that did contain some code, and also the GPL portion only concerns that API-calling layer, not what the model was trained on, or what it can output (which is what the GPL related mess about Copilot is about).
That is closed source. Also Kite does not seem comparable with GPT-3 or github copilot.