alexflint

14 ms·

31.
by alexflint 10y ago
Good idea - will look into it.
32.
by alexflint 10y ago
Right, but the python standard library docs are just a tiny tiny fraction of all the documentation in our index, and the documentation itself is just one corpus out of many.
33.
by alexflint 10y ago
It wouldn't be a viable business unless we thought we could add real value _and_ thought that we could capture some of that value. Yes, being on the cloud allows us to set up an attractive subscription model. But Kite won't succee
34.
by alexflint 10y ago
No we don't do anything with the terminal any more (and in particular we do not record terminal commands in any way)
35.
by alexflint 10y ago
We actually almost delayed launch to get linux support in because it's very close to ready. Several of us internally develop on linux and have been using Kite on linux for a while. Regarding features, there's actually more than ju
36.
by alexflint 10y ago
That's right: https://kite.com/tour/atom
37.
by alexflint 10y ago
I actually agree that under many languages/editors it's so difficult and finicky to set up autocomplete that it's not worth doing. We actually think that's a strength of the Kite model where we offload this stuff to the
38.
by alexflint 10y ago
Oops! That message is a remnant of the distant past and does not correspond in any way to what is actually happening under the hood.
39.
by alexflint 10y ago
Yeah, as of today (and probably for the foreseeable future) you can't use Kite while you're not connected to the internet. But honestly most programmers I speak to already rely a _lot_ on looking up material online while coding. K
40.
by alexflint 10y ago
Really, absurdly, ridiculously close. Like so close we almost delayed launch so that we could get it in.
41.
by alexflint 10y ago
(Copied from above.) Totally legit concern. when we started working on this we realized if we wanted to index tens of thousands of libraries, we wouldn't be able to ship the entire index along with the client. Hence the cloud-based arc
42.
by alexflint 10y ago
Sorry about this - it's embarrassing. We've been snowed under getting Kite ready for launch and didn't want to touch the update mechanism right before launch. We _will_ get this fixed ASAP. In the mean time, check out http:&
43.
by alexflint 10y ago
One of the big things we've worked on over the past few months is giving users fine grained control of which files are indexed by kite: - Kite only indexes directories that you have explicitly enabled - You can create a .kiteignore fil
44.
by alexflint 10y ago
Totally legit concern. when we started working on this we realized if we wanted to index tens of thousands of libraries, we wouldn't be able to ship the entire index along with the client. Hence the cloud-based architecture. We've
45.
by alexflint 10y ago
Great to hear - we'll be there soon :)
46.
by alexflint 10y ago
Thanks - we're investigating. Seems to be working in most places but there may be an edge node out of line.
47.
by alexflint 10y ago
Author here. Yeah using servo might be workable because you could test all your HTML ahead of time and work around any problems (unlike the any-browser web workflow). Still I agree re stable release.
48.
by alexflint 10y ago
Author here. I would expect binary sizes to end up similar to Electron since they will be dominated by libchromiumcontent, unfortunately.
49.
by alexflint 10y ago
Author here. I have been thinking about writing a react-like component system for Go, that outputs HTML. The major down side is that then you can't re-use much between your web-based app and your desktop app (which I think is a common
50.
by alexflint 10y ago
Author here. Yes this is a significant price to pay, but being able to test once and be sure that your users' experience will match your testing is worth a lot. It should be possible to have an updater that avoids downloading the main
51.
This Startup Entrepreneur Lives on Minimum Wage So He Has More Money to Donate(huffingtonpost.com)
51 points by alexflint 10y ago|12 comments
52.
Race and justice: much more than you wanted to know(slatestarcodex.com)
2 points by alexflint 10y ago|0 comments
53.
by alexflint 10y ago
Yes but how much CPU and memory are you willing to spare? Parsing is quite CPU-intensive, hence the CPU drag you often see when IDEs start indexing, and type inference involves a lot of unpredictable lookups all over the index, so much of i
54.
by alexflint 10y ago
Actually kite does not index any directories that you haven't explicitly enabled. So it's really easy to enable it for some but not all of your codebases.
55.
by alexflint 10y ago
The main difference versus IDEs is that everything we show is informed by all the public code we've collected from the web. So e.g. there are a ton of arguments to matplotlib.plot and IDEs can show you them all ranked alphabetically, w
56.
by alexflint 10y ago
No! If you can't see it (as visible chars) on your terminal then Kite is not seeing it.
57.
by alexflint 10y ago
1. Yeah, I agree. It's hard, and it's something we continue to iterate on. How would you feel about a global keyboard shortcut that would show/hide the overlay that was a separate application? 2. I love Rust. We will get to
58.
by alexflint 10y ago
Yeah this is something we're still iterating on. Though it wasn't in the demo video, there is actually a global keyboard shortcut to show/hide the sidebar without defocussing your editor. We're going to be experimenting
59.
by alexflint 10y ago
Absolutely. We're going to be working on this for many years, and this is the kind of thing we're aiming at.
60.
by alexflint 10y ago
Agreed.

More ›