> Our diagnosis is that individual developers do not pay for tools. I know this first hand, building a developer tool startup and failing to reach any level of revenue. In the end, the tech was bought out by a larger company to recover a fraction of our VC investment. The challenge is that when you're building software for developers, they already know how it must work. It's like trying to sell magic tricks to magici…
>> Our diagnosis is that individual developers do not pay for tools. Hijacking the quote... I can't count the number of times I see well-paid developers using the Sublime Text trial.
Kite is saying farewell and open-sourcing its code
271–280 of 547 posts
Re: Kite is saying farewell and open-sourcing its code
#272Re: Kite is saying farewell and open-sourcing its code
#273“Our 500k developers would not pay to use it. Our diagnosis is that individual developers do not pay for tools.” I don’t like depending on something I could lose in a month or tethers me to the internet. I consider that more a service than a tool. I’d prefer to just buy something once that just works, but that business model might be dead too since people will pirate things that aren't tethered to some serverside com…
Re: Kite is saying farewell and open-sourcing its code
#274I read about and tried evaluating Kite at the time and it seemed like it was in some kind of private invite stage. I remember thinking it must have been acquired and wasn’t taking new users. This must have been an incorrect take.
I’m surprised Tabnine is not mentioned in this thread at all, though because that was acquired and afaik is still operating.
Before copilot came along, Tabnine, not Kite, seemed like the ai took to beat.
I also remember a Python dev relations person from Jetbrains going on a podcast and clowning on AI code completion. That was in April of 2021. [2] A month later copilot dropped.
The very strange thing about that was Jetbrains described efforts to build an ML-based code completion plug-in in 2016! [3] It obviously failed to follow through on that.
I still think G Co pilot represents a threat to jetbrains IDEs overall. Even the packaged autocomplete can’t compete on basic stuff copilot does now.
I disagree with the idea that AI code completion is not good enough yet. I see that said all the time and yet it can masterfully fill in boiler plate today.
It can be way better, particularly in languages outside JavaScript and Python, but it’s usable now and maybe even profitable as a service if the business is not leveraged by VC capital.
If you listen to the September interview with Eddie Aftandilian of Github Copilot you would realize how early it still is for that product, as how to measure success in code completion is something still requiring behavioral patterns that are still being recorded.
Here’s the episode, listen 20 mins in: https://www.se-radio.net/2022/10/episode-533-eddie-aftandili...
[1] https://news.ycombinator.com/item?id=25074393
[2] https://twitter.com/jetsetter/status/1379438096232587265
[3] https://blog.jetbrains.com/idea/2016/09/share-your-stats-to-...
Re: Kite is saying farewell and open-sourcing its code
#275What?
You're supposed to create the technology, not wait for others to create it. That's why VCs give you money, isn't it?
> We built the most-advanced AI for helping developers at the time, but it fell short of the 10× improvement required to break through because the state of the art for ML on code is not good enough.
Aren't you supposed to advance the state of the art?
> but the problem is very engineering intensive
So you weren't a technology company?
Re: Kite is saying farewell and open-sourcing its code
#276> Our diagnosis is that individual developers do not pay for tools. I know this first hand, building a developer tool startup and failing to reach any level of revenue. In the end, the tech was bought out by a larger company to recover a fraction of our VC investment. The challenge is that when you're building software for developers, they already know how it must work. It's like trying to sell magic tricks to magici…
Sublime Text.
I sat through scores of interviews and pairing sessions with developers back when Sublime was a thing and the vast majority (>90%) of devs would rather exit out of that pop-up asking for support then pay the measly $30 or whatever regardless of their massive incomes and increased productivity that Sublime brought them.
We developers are no more altruistic than anyone else regardless of the lies we fed ourselves in the early days of FOSS, internet, bitcoin, etc.
:(
Re: Kite is saying farewell and open-sourcing its code
#277> Our diagnosis is that individual developers do not pay for tools. I know this first hand, building a developer tool startup and failing to reach any level of revenue. In the end, the tech was bought out by a larger company to recover a fraction of our VC investment. The challenge is that when you're building software for developers, they already know how it must work. It's like trying to sell magic tricks to magici…
- time
- headache
- improve my quality or quantitive results
I very often do not want to pay if the product isn't as good as it claims or simply not good enough.Software developers very simply would rather build their own half assed solution to a problem rather than pay for a half assed solution.
Offer quality, we'll pay.
Re: Kite is saying farewell and open-sourcing its code
#278Earlier quoted context omitted.
This is a product that I actually _would_ pay for as an individual. It's reasonably priced and worth the increase in efficiency and better experience. Plus their pricing is fair and flexible.
Yes, it seems fair to me to spend real money on Jetbrain's tools, if you like them. It is strange how reluctant programmers are to spend on tools even though they are, as a rule, quite willing to let themselves be paid handsomely for their services. Yet graphic designers pay for Adobe's tools. Who can read this riddle?
Important caveat here. My only exposure to JetBrains had been through Intellij which was thoroughly unpleasant around 2012-2013. That impression has left me forever sour towards them. Surprised to hear people say that it could be a step up from VSCode.
It looks like "Fleet" is their VSCode competitor? I'm not sure if the homepage does a good job at communicating how this improves over of VSCode. First of all VSCode has an enormous ecosystem of tools which seems hard to replicate. In terms of advertised features for Fleet, it seems like the one most highlighted on the page is multiplayer, which would possibly enable others watching me code live? Sounds nerve-wracking. Although I could imagine some helpful scenarios when pair-programming or something.
Other items that are advertised don't really encourage me to want to make the leap, especially as something I have to pay for. It sounds like they could host your code, or something like that, which could be nice. An annoying part of my workflow is that I work on the same codebase between multiple machines and every time I hop between machines I have to commit the changes to a private repository that is separate from my team's repository. It seems like it would be somewhat straight-foward to have the same code shared between all machines.
Other than that I would be interested to hear on how any Jetbrains products would improve productivity.
Re: Kite is saying farewell and open-sourcing its code
#279Earlier quoted context omitted.
Yes, it seems fair to me to spend real money on Jetbrain's tools, if you like them. It is strange how reluctant programmers are to spend on tools even though they are, as a rule, quite willing to let themselves be paid handsomely for their services. Yet graphic designers pay for Adobe's tools. Who can read this riddle?
Because developers want to be able to hack on their own tools: fix bugs, add features, whatever. Graphics designers do not have the skills to hack on their own tools, so there isn't a huge population of them sitting around going "damn, I wish I had feature X -- I know, I'll build my own editor and open source it!"
Re: Kite is saying farewell and open-sourcing its code
#280Earlier quoted context omitted.
If Copilot generates the exact same code as the source, I don't see how that process could be exempt, it's like using the clipboard on your PC with extra steps.
It can generate the same code, but generally won't.