Oh this is really neat for the Bazel community, as depending on tree-sitter to build a gazelle language extension, with Gazelle written in Go, requires you to use CGO. Now perhaps we can get rid of the CGO dependency and make it pure Go instead. I have pinged some folks to take a look at it.
Show HN: I ported Tree-sitter to Go
61–70 of 116 posts
Re: Show HN: I ported Tree-sitter to Go
#62Earlier quoted context omitted.
Also, evil maids, what?
I can't speak for the specificity of parent's "evil maids" phrase but the concept of an "Evil maid" is used in security scenarios. A maid tends to be an example of a person who's mostly a stranger, but is given unmonitored access to your most private spaces for prolonged periods of time. So they theoretically become a good vector for a malicious actor to say "hey I'll give you $$ if you just plug in this USB drive in…
Re: Show HN: I ported Tree-sitter to Go
#63Claude attempted a treesitter to go port Better title
How is OP using Claude relevant?
I, for one, am definitely not going to use this project for anything serious unless I have thoroughly reviewed the code myself. Prototyping is fine.
Re: Show HN: I ported Tree-sitter to Go
#64Earlier quoted context omitted.
Wait, are you suggesting that OP broke in to your server and stole code and is republishing it as these repos? I have questions. Have you reviewed the code here to see if it matches? What, more specifically, do you mean when you say someone broke in? What makes you think that this idea (which is nice but not novel) is worth stealing? If that sounds snarky, it’s not meant to; just trying to understand what’s going on.…
1. Just saying, strange coincidence 2. How can we compare Claude's output in a different language? 3. Detecting break-ins and handling evil-maids: unless the trick is already known on the internets, I do not disclose. Odds are not in my favor. 4. Maybe worth, maybe not. I have my adaptations. Trying to make it not worthy of stealing, in fact.
Re: Show HN: I ported Tree-sitter to Go
#65Re: Show HN: I ported Tree-sitter to Go
#66Re: Show HN: I ported Tree-sitter to Go
#67Wouldn't `got` be confused with OpenBSD's Got: https://gameoftrees.org/index.html
Re: Show HN: I ported Tree-sitter to Go
#68Earlier quoted context omitted.
How is OP using Claude relevant?
OK for prototyping. Not OK for prod use if noone actually read it line by line.
It feels to me like a lot of this is dogma. If the code is broken or needs more testing, that can be solved. But it’s orthogonal: the LLM can be used to implement the unit testing and fuzz testing that would beat this library into shape, if it’s not already there. It’s not about adding a human touch, it’s about pursuing completeness. And that’s true for all new projects going from zero to one, you have to ask yourself whether the author drove it to completeness or not. That’s always been true.
You want people to hedge their projects with disclaimers that it probably sucks and isn’t production worthy. You want them to fess up to the fact that they cheated, or something. But they’re giving it away for free! You can just not use it if you don’t want to! They owe you nothing, not even a note in the readme. And you don’t deserve more or less hacker points depending on whether you used a tool to generate the code or whether you wrote it by hand, because hacker points don’t exist, because the value of all of this is (and always will be) subjective.
To the extent that the modern tools and models can’t oneshot anything, they’re going to keep improving. And it doesn’t seem to me like there’s any identifiable binary event on the horizon that would make you change your mind about this. You’re just against LLMs, and that’s the way it is, and there’s nothing that anyone can do to change your mind?
I mean this in the nicest way possible: the world is just going to move on without you.
Re: Show HN: I ported Tree-sitter to Go
#69Earlier quoted context omitted.
OK for prototyping. Not OK for prod use if noone actually read it line by line.
I’m just curious, what would need to happen for you to change your opinion about this? Are you basically of the opinion that it’s not good enough today, never will be good enough in the future, and we should just wind back the clock 3 years and pretend these tools don’t exist? It feels to me like a lot of this is dogma. If the code is broken or needs more testing, that can be solved. But it’s orthogonal: the LLM can…
If the community majority changes it mind then so be it. But the fight will continue for quite some time until that is decided.