News for hackers. Stuff that matters.
Re:OpenCode – The open source AI coding agent by petcat on Saturday March 21, 2026 @07:18AM (#47466015)
> It's more accessible to contributors.

What would make go more "accessible to contributors" than Rust?

Re:OpenCode – The open source AI coding agent by ksh09 on Saturday March 21, 2026 @08:11AM (#47466313)
Mature tui packages like bubbletea, lipgloss. Besides TS resemblance to go could push the movement of rewrite, not necessarily easier though.

CC isn't foss in the first place, so the previous comment falls short.

Re:OpenCode – The open source AI coding agent by jeremyjh on Saturday March 21, 2026 @10:29AM (#47467361)
> TS resemblance to go

This is the second time I've seen claims like this in the last 24 hours and I'm afraid I might have lost contact with reality.

Re:OpenCode – The open source AI coding agent by yoz-y on Saturday March 21, 2026 @07:53AM (#47466207)
Go is a language one can learn and become functional in an afternoon. Rust is way more involved.
Re:OpenCode – The open source AI coding agent by Yokohiii on Saturday March 21, 2026 @08:14AM (#47466326)
To vibe coders it doesn't matter, right?
Re:OpenCode – The open source AI coding agent by kelipso on Saturday March 21, 2026 @09:03AM (#47466642)
Even then, you still need to read that code and Rust is way less read friendly than Go.
Re:OpenCode – The open source AI coding agent by Yokohiii on Saturday March 21, 2026 @09:32AM (#47466879)
I have the impression that most vibe coders don't read code. I guess they would probably use something accessible to them, just in case.
Re:OpenCode – The open source AI coding agent by seunosewa on Saturday March 21, 2026 @02:24PM (#47469784)
Successful vibe coders read code.
Re:OpenCode – The open source AI coding agent by MarsIronPI on Saturday March 21, 2026 @10:34PM (#47473895)
I'm looking forward to watching Gas Town catch fire, if and when it does.
Re:OpenCode – The open source AI coding agent by Andrei_dev on Saturday March 21, 2026 @05:41PM (#47471735)
I've been poking at AI-generated apps from the security side and yeah, reading the code is only half the problem. The code that IS there usually works. It's what's missing that gets you — no input validation, secrets sitting in plaintext, auth that the UI enforces but the server doesn't.

And even if you do read every line, you still won't catch it unless you know what should be there but isn't. No security headers. No RLS. System prompts wide open to injection. That stuff requires knowing the checklist, and the AI never had one.

Re:OpenCode – The open source AI coding agent by Yokohiii on Sunday March 22, 2026 @09:51AM (#47477564)
LLMs should know that, for maybe a CRUD app, there should be taken care of security at various layers, i.e. input validation in controllers. Knowledge from popular frameworks that communicate security boundaries should be transferable for them, even if everything is custom code. Very confusing to me how they manage to completely ignore so much of it. I guess they are too good following suit of a productivity minded vibe coder.
Re:OpenCode – The open source AI coding agent by olmo23 on Saturday March 21, 2026 @10:59AM (#47467650)
If you already know some php python javascript and/or c, you can pretty much just wing with Claude code.
Re:OpenCode – The open source AI coding agent by _flux on Saturday March 21, 2026 @10:50AM (#47467564)
Frankly I don't think one even needs to learn it, if you know a bunch of other languages and the codebase is good. I was able to just make a useful change to an open source project by just doing it, without having written any lines of Go before. Granted the MR needed some revisions.

Rust is my favorite, though. There are values beyond ease of contribution. I can't replicate the experience with a Rust project anymore, but I suspect it would have been tougher.

Re:OpenCode – The open source AI coding agent by verandaguy on Saturday March 21, 2026 @11:52AM (#47468138)
My personal opinion is that I like Rust much more than Go, but I can’t deny that Rust is a big, and more dauntingly to newcomers, pretty unopinionated language compared to Go.

There are more syntax features, more and more complex semantics, and while rustc and clippy do a great job of explaining like 90% of errors, the remaining 10% suuuuuck.

There’s also some choices imposed by the build system (like cargo allowing multiple versions of the same dep in a workspace) and by the macro system (axum has some unintuitive extractor ordering needs that you won’t find unless you know to look for them), and those things and the hurdles they present become intuitive after a time but just while getting started? Oof