Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The clear dark pattern here should also have been addressed: Kite is listed with all its shiny features, whereas the alternative simply gets called inaccurate and incomplete. Local analysis does have some clear advantages over Kite, even excluding important privacy concerns. What if you're offline or are in an area with poor network coverage?

https://kite.com/static/media/autocomplete-python-flow.690d3...

The use of dark patterns is more of a policy/"culture" thing that people won't exactly "knock" (although there was a comment on the HN thread last week about this) or demand the removal of, but it does speak to how Kite is willing to operate, not just pre-minimap fiasco, but going forward too.

Edit:

The link to the PR in the post isn't the point here, it's the propensity to write misleading copy targeted at thousands of devs who had never heard of Kite that went unaddressed. Open source is extremely trust-based (how hard was it to believe that a text editor plugin of all things was doing funny things?), and Kite needs to talk about whether it will continue to behave as a potential bad actor.

Right now, all the post contains is an apology for a PR fiasco that occurred due to something akin to a miscalculation, not a deliberate onboarding strategy.



https://github.com/kiteco/kite-installer/pull/50 was linked from the post, but it's not merged


It looks like they did (or are going to) address it: https://github.com/kiteco/kite-installer/pull/50




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: