31–40 of 70 posts
what visualization library is used -- looks cool -- maybe we could adapt it to other use cases that can benefit from a graph visualization
according to packages: https://github.com/cosmtrek/mindwalk/blob/master/web/package...
Other than being aesthetically pleasing (which it doubtlessly is), what's the use case for this?
> It's pretty, but I can't think of anything I'd use it as a "tool" for. - https://news.ycombinator.com/item?id=21560013
Seems any time this sort of software comes up on, people can't let the use case be "this is aesthetically pleasing".
Anyways, besides that, the README does clearly state "The Problem" and "The Idea" which outlines exactly why the author built this particular project.
Other than being aesthetically pleasing (which it doubtlessly is), what's the use case for this?
2019, in a comment about gource: > It's pretty, but I can't think of anything I'd use it as a "tool" for. - https://news.ycombinator.com/item?id=21560013 Seems any time this sort of software comes up on, people can't let the use case be "this is aesthetically pleasing". Anyways, besides that, the README does clearly state "The Problem" and "The Idea" which outlines exactly why the author built this particular project…
I asked about the use case _because_ the readme states a problem but does not offer a solution to that problem as far as I could see.
Sort of like gource?
Wow, it's my first time learning it. The visualization seems similar.
Earlier quoted context omitted.
2019, in a comment about gource: > It's pretty, but I can't think of anything I'd use it as a "tool" for. - https://news.ycombinator.com/item?id=21560013 Seems any time this sort of software comes up on, people can't let the use case be "this is aesthetically pleasing". Anyways, besides that, the README does clearly state "The Problem" and "The Idea" which outlines exactly why the author built this particular project…
> Anyways, besides that, the README does clearly state "The Problem" and "The Idea" which outlines exactly why the author built this particular project. I asked about the use case _because_ the readme states a problem but does not offer a solution to that problem as far as I could see.
Use case is to monitor agents activity.
Other than being aesthetically pleasing (which it doubtlessly is), what's the use case for this?
2019, in a comment about gource: > It's pretty, but I can't think of anything I'd use it as a "tool" for. - https://news.ycombinator.com/item?id=21560013 Seems any time this sort of software comes up on, people can't let the use case be "this is aesthetically pleasing". Anyways, besides that, the README does clearly state "The Problem" and "The Idea" which outlines exactly why the author built this particular project…
Earlier quoted context omitted.
2019, in a comment about gource: > It's pretty, but I can't think of anything I'd use it as a "tool" for. - https://news.ycombinator.com/item?id=21560013 Seems any time this sort of software comes up on, people can't let the use case be "this is aesthetically pleasing". Anyways, besides that, the README does clearly state "The Problem" and "The Idea" which outlines exactly why the author built this particular project…
I agree with all of this, and gource is an excellent example, but this is still "what" and builds no case for a "why". Not even an anecdote like "I told the agent this and it completely misunderstood and did the other thing so I built this which you can use to undo the work after the fact."