For most CRUD apps running in docker its enough to just tell the "agent" to use podman.

HackerNews is social media and this is just representative of social media as a whole.

Critical thinking is at an all time low to start with but even if you attempt to think critically while using social media you cannot do it constantly. This is one of the problems with social media as a whole. You might notice one thing is not quite right and discard it but you cant do that constantly and eventually you will absorb one of the 15 posts or comments.

As a dev I would tell you its an ops burden.

My devops coworker just shrugs, pumps out some yaml and helm and away it goes.

It really depends on your experience and tolerance for a lot of things.

Usually maintenance burden doesent start to make itself known till you get off the happy path or something breaks. Sometimes it can be a long while before that happens, sometimes it happens right away.

I have heard people use smoke test but not nearly at the same rate an LLM uses.

If a repo is bare of CLAUDE.md but mentions a smoke test in a commit in the last year I assume it to be LLM written.

At my last two jobs, smoke tests were a common topic of conversation.

It isnt though.

The industry largely has selected for camp 1 long ago.

If you don't get immediate negative feedback camp 1 can go quite a ways before problems surface.

Camp 1 is winning because we did it. We built an artificial brain. Frontier models can think, reason, and produce code better than the average human programmer. (You have not met many actual programmers slaving away on enterprise code bases if you do not understand that this is the case; the self-selecting HN crowd does not represent the profession as a whole by a long shot.) It's just a matter of, how committed are you (is your organization) to really learning and leveraging the tools?

The use of LLMs has caused Rust usage to explode.

If youre not writing the code yourself and vibing away which I think most people generally are despite the disdain around here then why would you not choose the "more performant language" (I know that isnt necessarily reality but it is a common perception).

Go's managed runtime is less valuable when the LLM is perfectly happy to slap a bunch of stuff together for you to and approximate it and doesn't complain at all when writing async rust despite some of the rough edges.

Correction: The use of LLMs has caused every major language usage to explode.

And as mentioned in other comments, Rust slow compilation can be detrimental to LLMs + fast iteration speed. And it's not just speed, Tauri takes 20GB of disk space to compile. It's bonkers. This is npm/js ecosystem all over again but slower.

Another reason to pick Go if you're leaning on LLMs is the standard library. Often you can do more work with fewer dependencies.

I'd rather leverage world class engineers paid by Google to maintain dependencies for me than try my luck with half a dozen of 0.x crates. Plus stdlib APIs can (and are) versioned just like third party dependencies.

Fully agree with this. We use Rust in an enterprise setting for building web app backends and the experience is painful. A lot of crates just seem like someones side project. Too many ways to do things leads to bike shedding in PRs. Compile times are atrocious and can take like 30 mins to build.

Honestly using Go would have got us to the same point much quicker, with code that is much easier to review.

> And it's not just speed, Tauri takes 20GB of disk space to compile

I’ve worked with enough UI frameworks and large applications that this doesn’t sound unreasonable. It’s a smaller disk footprint than I’ve needed for several other C++ codebases with similar scope.

I like vibe coding but I am sceptical that a vibe coded runtime in Rust would be as awesome as the Go runtime which is written with deep expertise of Unix software and threading and many low level details that are subtle and do depend on global properties of the code to work flawlessly. It makes sense you can crank out Rust with an LLM if you know what you are doing, but if you want a GC type thing or preemptive scheduling across an N by M threading model, then you are competing against some very good code.

> the Go runtime which is written with deep expertise of Unix software

Go has no mmap(), import a 3rd party dependency for that and you'll get a segfault the very second you do a mistake.

Python has an mmap module which will catch many memory errors and present them as exception rather than causing a CVE.

I don't agree with the parent comment, but mmap is exposed (low-level) in the standard library and there's a high-level wrapper in x/exp. You need to be careful with mmap no matter where you're using it.

What Go mmap CVE were you thinking of?

> What Go mmap CVE were you thinking of?

Every time you see "segmentation fault", that right there is a CVE.

No, obviously.

Because you don't report and open the CVE, not because it isn't a security issue :)

No security practitioner agrees with you about this. Please don't troll.

I thought DOS was a security problem. Glad to learn differently!

Now your argument has become that only Go programs ever terminate unexpectedly. You can see why I've lost patience here.

I agree that agents make Rust a lot more tenable for less "kernel-and-browser"-demanding tasks than it was 4 years ago, but I do not agree that they eliminate the "managed vs. unmanaged runtime" question, and to the extent they influence any of this decisionmaking at all, you have to accept the notion of not reading the code. If you're reading it, it matters that Rust makes you do bookkeeping that managed runtimes avoid.

By that reasoning, we should all be vibing away C code. It's the most performant and efficient language out there, there's a ton of code out there the LLMs were trained on, and the complex logic of memory management is abstracted away by the LLM so you don't need to think about it.

Most people are not doing that though. There's probably a good reason, and it applies to other languages too.

There is a good chance that your vibe coded C program segfaults immediately upon running and contains lots of subtle logic errors, all of which requires many iterations (finding issues at runtime) before you program runs as expected.

With Rust, you'll likely get many compilation errors, but if your syntax is correct, compilation errors will be few, and your code will almost certainly just work.

I wouldn't build anything in C that I didn't absolutely have to, but, no, there is not in fact a good chance that your vibe-coded C program segfaults immediately.

In order to use C you need to actually understand it, also toolchain is more complex etc. Which makes it a no go for 99%.

Rust is so safe that anyone can vibe it without any idea what is going on there. Which is basically what is happening here.

And why rust is more used than go for vibecoding? Mostly because of hype and performance gains which 99.9% of projects do not need.

> performance gains which 99.9% of projects do not need.

most software isn't "needed"

> The use of LLMs has caused Rust usage to explode.

Rust had a "vibey" community long before vibecoding. In particular, it's long been fairly non-serious about yolo importing a bunch of crates to solve things (since the standard lib is small) which is kinda the same problem as having all those things just vibecoded. Either way, most projects weren't reading all of that other code!

> It is entirely possible to develop strong systems outside of your current skill and knowledge with methods like this.

If this is true how can you confidently make this assertion.

You yourself are not in a position to evaluate it, you are just running it through a couple times hoping for a "oh wait, you're right to call me out on that, that is not correct at all".

1. Tell it to find docs and research best practices.

2. Ask for references and read them.

> When done properly your own knowledge should have grown to meet the product you end up with.

I've found relying on my own research first for a local LLM works much better. Asking a biased source to find it's own research will result in biased research.

Elixir is pretty easy to learn.

Its syntax is very Ruby and everything is message passing / actors, or genservers.

If you have ever used actors at all it doesnt take much to pick it up and even if you havnt its pretty simple.

Its just designer furniture, like any other Velben good.

A designer couch made entirely of foam can cost you 10k just because there is a name on it.

You're paying for the distinctive style and to show others your wealth or taste.

The paranoia but also the naïveté of internet tracking is a bit of a rare combination I think. Shadow profiles have been a thing for 15 years or more and they have only gotten more sophisticated. Browser fingerprints are surprisingly unique. Unless this guy is rotating machines / vpns / using qubes / etc Google can very likely pinpoint within a degree of certainly which searches are theirs.

It isn’t paranoia when there are clear facts in here, the first fact is your queries are linked to your account, period. Second fact, you don’t control the server in any way or shape. Third, your identity is linked through your payment information, aka full legal details, not just through an IP. Comparing between all that and browsers fingerprinting is muddying the water, you can use searxng in the middle and anonymize the query, with no profiling cookies etc., adding few extra steps and it’s private for most people unless you are a person of interest, in kagi, this doesn’t exist! Even the anonymizer is ran by the same company, so much trust!

I am not paid to design kagi architecture nor I know the internals, but let’s say I can host that mentioned anonymizer myself (say in Canary Islands), and it pulls the queries from kagi who you have paid for by monero, then the company knows nothing about the user, no profiling, no tracking, nothing, that’s a great starting point.

If this doesn’t exist, using something like searxng is far better (privacy wise), not just as mentioned on how it’s more anonymous, but also it gives you the ability to blend in, rather than looking like a sore thumb in the logs.