Hacker Newsnew | past | comments | ask | show | jobs | submit | rane's commentslogin

That total assumes API billing rates, which isn't what Anthropic pays for the inference. So I'm confused why people keep quoting that. It's not representative of what it'd cost for you either because you could use cheaper models.


> That total assumes API billing rates, which isn't what Anthropic pays for the inference. So I'm confused why people keep quoting that. It's not representative of what it'd cost for you either because you could use cheaper models.

It is, because this rewrite was marketing for Claude. So it reflects the price for what other companies might need to pay if they want to rewrite something else with similar size.


Yeah, when you spend billions in infrastructure you get to save $300k occasionally


A new task manager to replace Taskwarrior

https://aven.raine.dev/


"Vibecoded" is not an accurate description of what actually happened. LLMs are extremely good at porting code from one language to another while preserving semantics. Which is why how everything turned out so well was not very surprising.


"Preserving semantics" by casting pointers to aliasing refs in Rust, ignoring lints and errors in the process.

Can't help laughing at this point.


I don't know, did the prior vibe-coded Zig code not ever have pointers aliased to data? Might be preserving semantics too well, if anything.


The Zig one uses raw pointers. These are bad and get out of hand quickly but at least don't have constraints like "you must never have two &mut on the same value". You may refer to c2rust to see how "semantics preserving transformation" without new UBs looks like.


You didn't read the blog post at all did you? Clearly you have zero clue what you are talking about.


Sorry, I did. And I did an internal sharing with respect to the blog post, on topics of how to (and not to) do software migration, how (not) to deal with unknown unknowns etc. We have several ongoing software (automated) migration projects so I did rather extensive research around it.

I do regret that I've also read the code though, otherwise I'd probably live a little happier with ignorance right now. Sadly as they don't know they don't know about the issues, there's no indication of those in the two public materials they have released.


It's extremely difficult to have a robust test suite for a TUI app like Claude Code. Hence regressions keep showing up in every update.


Absolutely can't wait to try this for language practice. The advanced voice mode is great but ultimately just doesn't work that well and doesn't have the feel of a natural conversation.


Try https://github.com/raine/claude-code-proxy

I canceled Claude plan a few months back and have been using this. OpenAI plans are much more generous.


The excessive emojis in the README don't inspire confidence


I thought so, and then I tried Opencode and Codex and started to appreciate Claude Code a lot more. They've actually done great work with the small details.


I actually have't looked back since trying opencode The ability to properly see what the agent is doing in tool calls and subagents is really unmatched, CC strips all reasoning and return values, only displaying tool calls, and you're unable to expand a single subagent, it's expand everything and scroll endlessly or show everything collapsed with basically no info at all (read x files, ran x commands) Just seems like extremely basic features are missing


I have 29 Claude Codes open, using 6.3 GiB RSS total


The point was to come up with a sensationalistic headline that HN eats up and post flies to the front page.


I wonder whether the title was generated/suggested by an AI?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: