spyglass VS difftastic

No direct experience but I saved some links about this:

https://wiby.me/about/guide.html

https://github.com/spyglass-search/spyglass

https://yacy.net/

Interesting thread(s) on HN about the last one:

https://news.ycombinator.com/item?id=32597309

I've been working on a self-hosted personal search app (https://github.com/spyglass-search/spyglass) and have recently been playing around with how to integrate it with local LLMs. I think this would be an awesome step into having your own personal assistant that can search through all your data and give you analysis / summaries.

We have an open-source desktop app (https://github.com/spyglass-search/spyglass) and are working on a web version that has more powerful features such as conversation search, check it out!

I'm one of the devs for Spyglass ([https://github.com/spyglass-search/spyglass](https://github.com/spyglass-search/spyglass)) an open-source personal search app. We're excited about all the advancements with language models recently and wanted to try merging the two ideas together to form something even better.

Another more recently available option is spyglass; it is more tenable than YaCy but dev is mostly on MacOS with focus on a desktop interface. I like the idea of web based interface.

I'm part of small team that's been building an open-source personal search engine (https://github.com/spyglass-search/spyglass). One of the major use cases is searching your local files & their contents which aligns perfectly with how Obsidian stores it notes.

I'm one of the developers of Spyglass (https://github.com/spyglass-search/spyglass), an open-source self-hosted personal search engine. We recently added the ability to search through your Reddit saved & upvoted posts!

i want a diff tool that shows me exactly which tokens have changed, and which haven't, regardless of how they are laid out.

These already exist: https://github.com/Wilfred/difftastic

when we get that, then we should get even less merge conflicts.

Counterintuitively, that is not the case. AST-merge is a much, much, much, much, much harder problem than AST-diff.

https://github.com/Wilfred/difftastic?tab=readme-ov-file#can...

The fact that diffs can be used to drive a 3-way merge is in fact an accidental property that arises due to the sheer crudeness of the diff format. As soon as you start using more-sophisticated diff formats, solutions to "the diff problem" no longer lead directly to solutions to "the merge problem".

Yes there is an `—-override` option you can use to specify the language in which a file should be parsed.

https://github.com/Wilfred/difftastic/blob/master/CHANGELOG....

Use the fantastic difftastic instead of git's diff. https://difftastic.wilfred.me.uk/

  [alias]

difftastic provides similar capabilities in a free tool based on treesitter

difftastic? https://github.com/Wilfred/difftastic

If you're looking for a VS Code extension or a GitHub app, check out https://semanticdiff.com/. I'm a co-founder of this project.

If you prefer a CLI tool, check out https://github.com/Wilfred/difftastic. It supports more languages, but doesn't recognize when code has been replaced by an equivalent version ("invariances"). So it will show some changes (e.g. replacing a character in a string with an escape sequence) even though they are technically equivalent.

Shameless plug: I've written difftastic[1], a tool that builds ASTs and then does a structural diff of them. You can use it with git too.

It's an incredibly hard problem though, both from a computational complexity point of view, and trying to build a comprehensible UI once you've done the structural AST diff.

[1]: https://github.com/wilfred/difftastic

There is a diff tool called difftastic: https://github.com/Wilfred/difftastic

The idea is that it does not show diff based on text change, but on syntastic meaning. For that, it uses tree-sitter.

I think it still shows the trailing comma in the situation as shown in the article, but it's quite different experience than the standard text based diff.