The very first page of the site should have examples of what you can do with it.
It’s such a shame to get this much traffic, and have it almost all bounce, because there’s no description of WHY someone would care.
Glean – System for collecting, deriving and querying facts about source code
81–85 of 85 posts
Re: Glean – System for collecting, deriving and querying facts about source code
#82Earlier quoted context omitted.
I don't recall which version of Emacs first had "go to definition", but it was well before the 90's.
How easy was it in 90’s to have a go to definition over, say, 10% of today’s maven central?
indexing speed probably wouldn't be a problem. the index size would probably exceed available disk space for a typical workstation of the time.
Re: Glean – System for collecting, deriving and querying facts about source code
#83Earlier quoted context omitted.
“Go to definition” has been around even longer, since at least the early 90s
I don't recall which version of Emacs first had "go to definition", but it was well before the 90's.
ctags came about in 1992. etags was a little bit later.
was there something before etags in emacs?
Re: Glean – System for collecting, deriving and querying facts about source code
#84Earlier quoted context omitted.
I don't recall which version of Emacs first had "go to definition", but it was well before the 90's.
ctags came about in 1992. etags was a little bit later. was there something before etags in emacs?
The wiki page says ctags was part of the 3BSD release, which would put it about 1979. My memory isn’t good enough to recall which release of emacs picked up support.
I think there was a find-function key binding for lisp code before ctags, but these are very rusty bits I’m recalling.
Re: Glean – System for collecting, deriving and querying facts about source code
#85Earlier quoted context omitted.
I'm really struggling to understand what Glean does, and why I would use it. Most important: Your landing page should quickly show what Glean does that a typical IDE (Visual Studio, Visual Studio Code, Eclipse, ect, does.) Specifically, things like "Go to definition," and tab completion have been in industry-leading IDEs for at least 20 years. What's novel about Glean? It seems like a lot of hoops to jump through whe…
> It seems like a lot of hoops to jump through when Visual Studio (and Visual Studio Code) can index a very large codebase in a few seconds. I think you are not thinking large enough. An IDE absolutely can not index a very large codebase and allow users to make complex queries on it. Think multiple millions lines of code here. The use case is closer to "find me all the variables of this type or a type derived from it…
> Think multiple millions lines of code here. The use case is closer to "find me all the variables of this type or a type derived from it in all the projects at Facebook" than "go to this definition in the project I'm currently editing".
That wasn't clear, at all.
Maybe they could just say exactly what you said?