HN user

phrotoma

679 karma

[ my public key: https://keybase.io/rsalmond; my proof: https://keybase.io/rsalmond/sigs/z-FJ2_XvqqXk_pYewdsUeauz9FrCbGHIb-gSxvOBIrw ]

Posts0
Comments264
View on HN
No posts found.

True that an interpreted language has a leg up on any compiled language in the arena of compile time, but worth noting that one of Go's primary design goals was improving compile times of massive code bases. Google was drowning under the weight of compiling huge C++ codebases and Go was the response to that (among other things).

It's not slick, but I've always labeled this as; answering the question they want to answer (rather than answer the question that was asked).

I love this site design. It uses the entire width of the monitor rather than a slender column of pixels down the middle with large blocks of unused space on either side, with a font for my old man eyes.

<3

Even the glass dishes with tiny bubbles and imperfections, proof they were crafted by the honest, simple, hard-working indigenous peoples of wherever.

Accelerando (2005) 2 months ago

Same. Although tbf this is a defining feature of many of my favourite sci-fi novels. Whenever I revisit the Sprawl or the Bridge trilogies I always notice something I completely missed before.

Show HN: Nibble 2 months ago

Intermediate Representation. It's an architecture independent "halfway point" that happens during compilation, in between reading the source code and writing the binary. It's part of the approach that makes it possible for LLVM to "plug-in" a new target architecture by just adding a bit that turns IR into machine code for the new chip.

I'm oversimplifying because it's all black magic to me, but I do know that acronym.

you've strayed off the golden path & are attempt to do something the wrong way (in Talos world).

In this case the urge to make a tweak is synonymous with the urge to make the product _function_.

I admire their dedication to the schtick, but the upshot is that since you cannot reach inside to make Talos actually work in environments that aren't supported by that golden path, running the product on many devices is "Talos Wrong".

That's their perrogotive, but it's obnoxious in a "Windows 11 doesn't work on your perfectly functional laptop" kinda way.

My primary use case for K3s is small machines, cheap VPS, Pi, etc. Would love to hear from folks who have had success with Talos in those spaces but last time I gave it a shot the welded shut hood prevented me from doing the little tweaks necessary to get running in those environments.

In the cloud or on prem I suspect folks are having better luck than I did, but also open to being wrong about this.

K8s encourages thinking about workloads as "cattle not pets". App running in K8s falls over? Blow it away and let K8s recreate it, etc.

However clusers themselves often become the new pets. Many orgs do not reach a level of operational maturity where they can blow away and recreate whole clusters without downtime and toil.

A meta-pattern has emerged where higher order tooling managers a whole fleet of clusters. This is an implementation of that meta pattern which uses K8s itself as the higher order tool to manage other clusters.

It's not a new idea, just a new implementation of the pattern.

It is very close, but what's more interesting to me is that it's actually amusing. I've yet to see an LLM actually be originally funny (entirely possible I've missed the crossing of that line) and the opening lines put a wry grin on my face.