Live data from Hacker News

The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

alex000kim.com

501–510 of 636 posts

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#501

Earlier quoted context omitted.

"frontier" as in the frontier of using everybody else's code, books, art of everyone else for a specific purpose that was never intended to, as in, not even open source projects ever imagined LLMs becoming a thing and their licenses reflected as much.

You have a very poor understanding of LLMs if you think that is the frontier today. Maybe in 2024 it was.

Please educate us then.

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#502

I am still just shocked that Claude Code was written in Typescript, not C++, Rust or Python. It also somehow messed up my alacritty config when I first used it. Who knows what other ~/.config files it modifies without warning.

I'm surprised Python is on that list. TypeScript doesn't seem like a terrible choice, as it can leverage vast ecosystems of packages, has concurrency features, a solid type system, and decent performance. C++ lacks as robust of a package ecosystem, and Python doesn't have inbuilt types, which makes it a non-starter for larger projects for me. Rust would have been a great choice for sure.

> I'm surprised Python is on that list.

I mostly mentioned it because it is pre-installed on some (linux) systems. Though of course if you're trying to obfuscate the sourcecode you need to bundle an interpreter with the code anyway.

But it has historically been used for big programs, and there are well established methods for bundling python programs into executables.

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#504

I am still just shocked that Claude Code was written in Typescript, not C++, Rust or Python. It also somehow messed up my alacritty config when I first used it. Who knows what other ~/.config files it modifies without warning.

Anthropic acquired Bun. Clearly, Bun is not a runtime for C++, Rust, or Python. For an engineering project, strongly typed TypeScript was basically the only possible choice for them.

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#505

I am still just shocked that Claude Code was written in Typescript, not C++, Rust or Python. It also somehow messed up my alacritty config when I first used it. Who knows what other ~/.config files it modifies without warning.

Anthropic acquired Bun. Clearly, Bun is not a runtime for C++, Rust, or Python. For an engineering project, strongly typed TypeScript was basically the only possible choice for them.

I am not following your logic. Anthropic acquired Bun and so all of their end-user software should use it?

Or am I missing sarcasm?

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#506
post #249

Earlier quoted context omitted.

That’s how I’d want it to be honestly. LLMs are tools and I’d hope we’re going to keep the people using them responsible. Just like any other tools we use.

It’s also pretty damn obvious when LLMs write code. Nobody out here commenting every method in perfect punctuation and grammar.

I have been doing this for years, especially for libraries (internal or otherwise), anything that's `pub`/`export`, or gnarly logic that makes the intent not obvious. Not _everything_ is documented, but most things are.

I'm doing it because I know how much I appreciate well-written documentation. Also this is a bit niche, but if you're using Rust and add examples to doc-comments, they get run as tests too.

Also given we both managed to produce more than one sentence, and include capital letters in our comments, it's entirely possible both of us will be accused of being an AI. Because, you know... People don't write like this, right?

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#507
But what does Claude do when it detects user fruatration?! Don't leave us hanging here!

Edit: it gets sent to Anthropic via telemetry and it ends up on the fuck chart!

https://old.reddit.com/r/ClaudeCode/comments/1s99wz4/boris_t...

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#509
post #296

Earlier quoted context omitted.

+1. If we’re at an early stage in the agentic curve where we think reading commit messages is going to matter, I don’t want those cluttered with meaningless boilerplate (“co-authored by my tools!”). But at this point i am more curious if git will continue to be the best tool.

I'm only beginning to use "agentic" LLM tools atm because we finally gained access to them at work, and the rest of my team seems really excited about using them. But for me at least, a tool like Git seems pretty essential for inspecting changes and deciding which to keep, which to reroll, and which to rewrite. (I'm not particularly attached to Git but an interface like Magit and a nice CLI for inspecting and manipul…

Of course git is great!

Check out Mitchell Hashimoto’s podcast episode on the pragmatic engineer. He starts talking about AI at 1:16:41. At some point after that he discusses git specifically, and how in some cases it becomes impossible to push because the local branch is always out of date.

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#510

I am still just shocked that Claude Code was written in Typescript, not C++, Rust or Python. It also somehow messed up my alacritty config when I first used it. Who knows what other ~/.config files it modifies without warning.

I'm surprised Python is on that list. TypeScript doesn't seem like a terrible choice, as it can leverage vast ecosystems of packages, has concurrency features, a solid type system, and decent performance. C++ lacks as robust of a package ecosystem, and Python doesn't have inbuilt types, which makes it a non-starter for larger projects for me. Rust would have been a great choice for sure.

Python and C++ have been used for countless large projects— each one for many more than typescript. It’s all about trade-offs that take into account your tasks, available coders at the project’s commencement, environment, etc.
Post reply on HN