An apology that starts with 4 paragraphs of self-congratulation is not a real apology at all. Nothing of the article reads as being genuinely regretful of the strategies taken - it's just sorry for being caught. >Unfortunately, while trying to make programmers’ lives a little less complicated, we instead made them more complicated. Barely an admission of guilt, and even that can't get past without patting themselves…
The 2nd sentence is an apology: "Over the last few days, Kite has been knocked around in social media (and the actual media) over several moves we made to expand our user base. It was a humbling experience, and I’d like to apologize to the entire open source community for our handling of these projects."
Kite Responds to the Minimap and Autocomplete Issues
71–75 of 75 posts
Re: Kite Responds to the Minimap and Autocomplete Issues
#72Earlier quoted context omitted.
> I didn't say anything about race anywhere "lynch" is a racially-coded word in 2017. Google "lynch racially coded" and check the first few hits. That's the mine you unintentionally stepped on here.
I forgot I lived in 2017, where _literally_ anything can be taken out of context and made into a race issue.
Re: Kite Responds to the Minimap and Autocomplete Issues
#73Re: Kite Responds to the Minimap and Autocomplete Issues
#74This comment is very sightly off-topic for this story, but 100% on topic for HN, and so many people might find it useful that I feel compelled to write it. The first link in this write-up is to this story which gives the background: https://theoutline.com/post/1953/how-a-vc-funded-company-is-undermining-the-open-source-community And I wanted to draw attention to something remarkable from that write-up. Without any ir…
Re: Kite Responds to the Minimap and Autocomplete Issues
#75Earlier quoted context omitted.
Buying a popular addon with the express purpose of subverting its original intent for commercial monetization seems like it should be against Atom's TOS This instance is razor thin close to being malware What's to stop the next enterprising company from intentionally uploading all your code to their servers? Modifying your code? Or holding your code hostage? Atom has git support backed in, so how likely is it an addo…
Maybe Github should have an informal policy that punishes bad actors by penalizing how they're listed in Atom's built-in package browser. Or create a convention of documentation that is machine-readable and easy to preview in the editor's package-updater tool. But making blanket rules regarding commercialization would likely have unwanted unintended effects. FWIW, Atom's community manager wrote a long comment in one…
It would be challenging to be proactive about it, but it was be a clear solution when they get caught.