Guys it's not OK to just hijack open source projects. You need to make (or fork) new plugins specifically for kite, not hire a bunch of developers of popular autocomplete plugins and have them shadily change their plugin to use Kite as a completion engine.
they didn't. they just had them add _support_ for Kite. It was up to the user to enable it. I'm failing to see the issue here. I mean, yes, their UIs needed work, but they admitted to that mistake and have since fixed it (according to the article). Your comment makes me think this is more of an open-source lynch mob rather than someone looking at this objectively. Company needs users. Plugin has users. Plugin does th…
Kite Responds to the Minimap and Autocomplete Issues
11–20 of 75 posts
Re: Kite Responds to the Minimap and Autocomplete Issues
#12The title “Staying Open” is so full of BS it hurts.
Re: Kite Responds to the Minimap and Autocomplete Issues
#13Earlier quoted context omitted.
they didn't. they just had them add _support_ for Kite. It was up to the user to enable it. I'm failing to see the issue here. I mean, yes, their UIs needed work, but they admitted to that mistake and have since fixed it (according to the article). Your comment makes me think this is more of an open-source lynch mob rather than someone looking at this objectively. Company needs users. Plugin has users. Plugin does th…
"Lynch mob?" Really?
If you have nothing to actually add to the discussion, please keep your fingers tied.
Re: Kite Responds to the Minimap and Autocomplete Issues
#14I don't buy it. The UX was dark-patterned to enable this very thing, and this reads like damage control when it's clear it wouldn't fly under the radar.
If it were the last thing Kite wanted, there would be a big warning that this option uploads your code to their servers. Or some mention of the upload at all. Or it wouldn't be the foundation of Kite's business.
Re: Kite Responds to the Minimap and Autocomplete Issues
#15Guys it's not OK to just hijack open source projects. You need to make (or fork) new plugins specifically for kite, not hire a bunch of developers of popular autocomplete plugins and have them shadily change their plugin to use Kite as a completion engine.
On the one hand, I agree with the sentiment. On the other hand, if it is really that shady, it is on the open source developer to say 'no.' As described here, it doesn't seem that shady. There was a choice between Kite and Jedi for the one plugin, and for the other plugin, it was basically an AD. On the gripping hand, I really want open source developers to get paid, this seems like a way for open source developers t…
Re: Kite Responds to the Minimap and Autocomplete Issues
#16why u no Elixir support?
Re: Kite Responds to the Minimap and Autocomplete Issues
#17Guys it's not OK to just hijack open source projects. You need to make (or fork) new plugins specifically for kite, not hire a bunch of developers of popular autocomplete plugins and have them shadily change their plugin to use Kite as a completion engine.
they didn't. they just had them add _support_ for Kite. It was up to the user to enable it. I'm failing to see the issue here. I mean, yes, their UIs needed work, but they admitted to that mistake and have since fixed it (according to the article). Your comment makes me think this is more of an open-source lynch mob rather than someone looking at this objectively. Company needs users. Plugin has users. Plugin does th…
That's how you get installed an unwanted browser bar, a new amazing search engine, and the Norton security pack for 60 days.
If you see the screenshot carefully, by default they are asking permission to upload to their servers the content of your user directory "Enable access in Users/kite". Go and take a look at all the info you have in the subfolders of your user directory. [1]
My guess is that most people just expected that the current file was uploaded, not all the py files. Perhaps only the current line, not all the file. And many didn't read the dialogs and they just pressed enter.
[1] They only support Phyton, so they uploaded only the .py files, but I guess that in the future they can extend the search types to C and upload the .c, .cpp, .h, .inc, ... files too. Do they have to ask again or the current permissions are enough? What if they extend the search to .doc and .xls? What if they extend the search to images? Go again and take a look at all the info you have in the subfolders of your user directory.
Re: Kite Responds to the Minimap and Autocomplete Issues
#18Earlier quoted context omitted.
they didn't. they just had them add _support_ for Kite. It was up to the user to enable it. I'm failing to see the issue here. I mean, yes, their UIs needed work, but they admitted to that mistake and have since fixed it (according to the article). Your comment makes me think this is more of an open-source lynch mob rather than someone looking at this objectively. Company needs users. Plugin has users. Plugin does th…
The problem is that the screen was not clear enough. Users just press Continue, Continue, Agree, OK, Share all my user directory, Install, OK, Close. They never read the small or big letters, they just click the green button. The "Enable local engine" looks like a "Cancel" button. That's how you get installed an unwanted browser bar, a new amazing search engine, and the Norton security pack for 60 days. If you see th…
I'm probably not going to use their service any time in the future, but to imply they intentionally put users in the dark is kind of a stretch.
More like, they failed to communicate how their service worked. Also, they failed to provide a clear distinction between the two options for completion engines that described both objectively.
Honestly, it sounds to me like they were just overly-excited to sell their service, and didn't take a step back and say "hey, do you think this wording makes Jedi look a little overly-bad?" They could have done with some user-acceptance testing on this, for sure.
Re: Kite Responds to the Minimap and Autocomplete Issues
#19Re: Kite Responds to the Minimap and Autocomplete Issues
#20We were comfortable with this posture because the Atom/Sublime/VSCode plugin ecosystem has largely been dominated by honest OSS projects, especially the most popular ones. Thanks, Kite, for ruining that for everyone. I will now personally vet every plugin that my junior devs install from here out thanks to your example.