Why I Vibe in Go, Not Rust or Python • Hacker News Board

Re: Why I Vibe in Go, Not Rust or Python

#31

Post by cadamsdotcom » Mon, Mar 23, 2026, 8:57 PM UTC

Congratulations on learning to prompt websites into existence! It is a miracle we can do this.

It’s also great that you acknowledge the hard work of the humans that got Go into the great state it’s in.

Your blog post needs heavy edits to let your voice speak through over the AI you started from: for example, your headings say “The X.”, “The Y.” Please edit away the AI-isms before publishing. Leaving them in shows a lack of care, and I’m sure that is not the impression you wanted.

Re: Why I Vibe in Go, Not Rust or Python

#32

Post by riclib » Mon, Mar 23, 2026, 9:53 PM UTC

somesun wrote: post #27

what tts model do you use to make the audio , seems good can you share your prompt go make the website , what is the stack

the website is just using go standard library and templ. the voice is grok tts. the images are generate by nano banana from prompts written by claude, according to styles. it is all generated by a program called lg: https://yagnipedia.com/wiki/lg

the blog pages are markdown on disk, generated dynamically for each request, cached by cloudflare.

Re: Why I Vibe in Go, Not Rust or Python

#33

Post by Cthulhu_ » Tue, Mar 24, 2026, 1:42 PM UTC

riclib wrote: post #23

saidnooneever wrote: post #3

Earlier quoted context omitted.

every page includes inline css, js etc. so each load it will pull all of that in each time. so each page transfer. you could put the css and js parts that are common between them into separate files so that the browser can cache them and your users and server save some bandwidth. happy to see most of it looks kinda decent. Not sure why you promote the site as being built in Go because its html, css and javascript. Th…

Fair comment. In my production code I always separate out the css and embed it in the go binary as files that can be cached. Having it in embedded into the page was really useful to iterate behind cloudflare and not worry about css caching but is a terrible practice.

Counterpoint, inlining CSS / JS used to be an optimization in early website optimizers, because fetching multiple files incurred more HTTP overhead, and (...I think) compression was more efficient working on a single file vs three.

I don't think these arguments hold up anymore with http 2/3, but still, it used to be an optimization.

Re: Why I Vibe in Go, Not Rust or Python

#34

Post by Cthulhu_ » Tue, Mar 24, 2026, 2:35 PM UTC

Incipient wrote: post #22

I read the first two paragraphs, found a bunch of fairly glaring errors, and got put off. >It has type hints, which are optional, which means they’re not there. I mean it is there, and it works. I've also not had an AI make a dict key error in a while, but mostly as I use objects - haven't magic strings in code been bad for a while now? Also llms are bad at architecture, not things like typing or keys. I'm really str…

>>It has type hints, which are optional, which means they’re not there.

>I mean it is there, and it works.

The argument is that developers will avoid using things if they don't have to, especially if they're not used to it. But this isn't every developer nor an universal truth, just a jab at things.