Viewing profile — DarkPlayer
DarkPlayer
HN member- Joined
- Sun, Mar 24, 2013, 1:02 AM UTC
- HN karma
- 252
- Public activity
- 26 items
- HN profile
- View on Hacker News ↗
About DarkPlayer
No profile information was provided.
Recent public activity
-
comment
Comment #43557728
We observed the same behavior. Each request used a different IP address and a random user agent. In our case, most of the IP addresses belonged to Chinese ISPs. They went to great …
-
comment
Comment #42951146
> What we should have instead is syntax-aware diffs that can ignore meaningless changes like curly braces moving into another line or lines getting wrapped for reasons. These diffs…
-
comment
Comment #42949115
> However at a minimum formatting changes shouldn’t regularly complicate doing a diff. If the code needs to be reformatted, this should be done in a separate commit. Fortunately, t…
-
comment
Comment #42589655
Difftastic would not solve the issue described by madeofpalk because it still highlights the added comma. You need a diff tool that can distinguish between optional and required sy…
-
comment
Comment #42096528
Our parsers simply return the concrete syntax trees in a JSON format. We do not unify all the different syntax constructs into a common AST if that is what you are looking for. The…
-
comment
Comment #42096237
> - for diffing, the matching of the leaves is what matters the most, for merging the internal nodes are more important, The leaves are the ones that end up being highlighted in th…
-
comment
Comment #42095381
I don't think that different algorithms are better for merging or diffing. In both cases, the first step is to match identical nodes, and the quality of the final result depends he…
-
comment
Comment #42094842
Looking at the architecture, they will probably run into some issues. We are doing something similar with SemanticDiff [1] and also started out using tree-sitter grammars for parsi…
-
comment
Comment #41039144
You can find a comparison of the two tools here: https://semanticdiff.com/blog/semanticdiff-vs-difftastic/ As author of SemanticDiff, I am obviously a bit biased. But Wilfred, the …
-
comment
Comment #41038660
The VS Code extension works offline. The diff calculation is performed on the host where the VS Code GUI is running (makes a difference in case of SSH/Docker/WSL).
-
comment
Comment #41019476
Hi, author of SemanticDiff here. I'm sorry you didn't have a good experience testing the tool. If it doesn't work / makes things worse than a standard diff, that's definitely consi…
- story
- story
-
comment
Comment #39783065
> I am curious if there's been any work on _semantic_ diff tools as well (for when eg the syntax changes but the meaning is the same) We are working on https://semanticdiff.com/ wh…
-
comment
Comment #38373786
There are some tools that can separate actual code changes from reformatting changes. I am working on https://semanticdiff.com , a VS Code Extension / GitHub App that can help you …
-
comment
Comment #38211001
I think LLMs will have a hard time replacing traditional diff algorithms. You want your diff to be reliable and predictable. It shouldn't omit relevant changes. This is not really …
-
comment
Comment #36128799
I am working on a GitHub pull request viewer that displays changes using a semantic diff, and therefore has some more advanced whitespace handling behavior than just ignoring leadi…
-
comment
Comment #30846846
We are working on a code review tool which supports unified diffs with semantic diffing. If that sounds interesting for you, take a look at https://mergeboard.com
- story
- story
- story
- story
- story
- story
- story