In return they get an actually secure messing app they can use without having to support it themselves. Which is pretty big.

I thought land of the free and home of the brave was Scotland

https://blog.giovanh.com/blog/2025/10/14/a-hack-is-not-enough/ this article makes a sadly excellent point in response to you here. Fair warning: it’s long. But even if you dip out early I assume you’ll get the point being made

Ok fair, sorry for being snappy, I think fusion is cool and probably pretty close these days and get a bit defensive when I feel I’m misrepresented.

Wow, that’s not my attitude at all, I said ‘not there yet’, I’m sorry you can’t read bro

Fusion power ain’t there yet though, bad example?

And there’s no Tim Curry, who frankly makes RA2

Oh well that’s depressing. I last interviewed about 3 years ago and I guess it might well have changed overall. OTOH I get to run the interviews where I’m at now and I can assure you that ‘actually using your available resources’ would never be a problem :)

We let people use chatbots in our technical interview and don’t even mark down for it, since they’re a tool that exists.

I have yet to see a candidate who uses chatbots be anywhere near as good at producing good solutions quickly as the ones who don’t.

In reverse order:

• Directly mapping structs to JSON is a solved problem in userland for every major language
• yes it does, and worse it’s part of the return signature and null is super-prevalent of necessity as a result
• even java doesn’t do that any more, but fine I guess
• cool, but access modifiers actually make a lot of sense. Go’s solution to this is to use capitalisation as a marker, which has no ‘inferential readability’ – public/private is obvious. Foo/foo? Considerably less so

Further, meta programming in go sucks donkey balls. Sure, it finally got generics but also they suck. Last I checked it still didn’t even support covariance.

Dude, weird ass-comment. I can share my opinions and they don’t have to be positive ones. Go is a tool and its purpose is to be an aesthetic stain on the realm of software.

Thank you for your attention

That’s completely fair, thank you for your service

Ironically Go is such a shite verbose language that basically everyone I know who has to work with it will use an llm code-assistant tool to avoid having to write all the boilerplate themselves.

I know of no other language that comes close to prompting the level of LLM-dependency that Go inspires.

Edit: well, seems like this goes against the popular consensus but I stand by my guns if the down votes are from average Go enjoyers. If, on the other hand, the down votes are at the sentiment that even Go should not be vibe coded, I can at least agree with that, but who knows what jimmies I’ve rustled

Yeah that’s widely considered to be the article about it tbh

Funnily enough my eldest is getting a laptop this Christmas. Arch Linux with a heavily locked-down environment (I’ve disabled WiFi on the non-root account, even). She’s just about to turn 7 – how old are yours?

Well time will tell won’t it, but we’re both just guessing at the end

No that’s way too paranoid. Honestly 20 years not 6 months. And by then ladybird will be viable so nbd

They got the punctuation all mixed up. Instead of ‘Windows 10 will be the last ever version! No more major upgrades!’ it was meant to read ‘Windows 10 will be the last ever version? No! More major upgrades!’

Unfortunate mistake

Maybe worried about looking personally identifiable. It’s understandable.

Which is weird because if you’re actually trying to get shit done, you get much more value out of someone with experience in your ecosystem than someone you’ve just hired, and it’s astonishing how low you an keep those ppls salaries compared to new hires who’re much less effective. Hire+fire is shit for everyone. Except, I guess, idiots who can only think 2 months in either direction.