- Great, and thank you.
I really, really appreciate that Garage accommodates running as a single node without work-arounds and special configuration to yield some kind of degraded state. Despite the single minded focus on distributed operation you no doubt hear endlessly (as seen among some comments here,) there are, in fact, traditional use cases where someone will be attracted to Garage only for the API compatibility, and where they will achieve availability in production sufficient to their needs by means other than clustering.
- No tags on objects.
Garage looks really nice: I've evaluated it with test code and benchmarks and it looks like a winner. Also, very straightforward deployment (self contained executable) and good docs.
But no tags on objects is a pretty big gap, and I had to shelve it. If Garage folk see this: please think on this. You obviously have the talent to make a killer application, but tags are table stakes in the "cloud" API world.
- > to bash MS products.
Microsoft gives them a lot of ammo. While, as I said, Microsoft et al. have seen that SMB is indeed efficient, at the same time security has been neglected to the point of being farcical. You can see this in headlines as recent as last week: Microsoft is only now, in 2025, deprecating RC4 authentication, and this includes SMB.
So while one might leverage SMB for high throughput file service, it has always been the case that you can't take any exposure for granted: if it's not locked down by network policies and you don't regularly ensure all the knobs and switches are tweaked just so, it's an open wound, vulnerable to anything that can touch an endpoint or sniff a packet.
- Why not? SMB is no slouch. Microsoft has taken network storage performance very seriously for a long time now. Back in the day, Microsoft and others (NetApp, for instance,) worked hard to extend and optimize SMB and deliver efficient, high throughput file servers. I haven't kept up with the state of the art recently, but I know there have been long stretches where SMB consistently led the field in benchmark testing. It also doesn't hurt that Microsoft has a lot of pull with hardware manufacturers to see their native protocols remain tier 1 concerns at all times.
- I have a cheap samsung from 5 years ago that pops up a dialog when it boots. I've never read it or agreed to it. It goes away after about 5 seconds. After that I stream using HDMI and all is well. It's also never been connected to a network.
Can't say what other TVs do, but this one works fine without TOS etc. If there is some feature or other that doesn't work due to this, I can say I've never missed it.
- In Lansing, it was below freezing and windy most of the day. If I noticed 100 people standing around on the pavement for hours in that, I'd probably imagine they deserved at least some regard for their concerns. But then, I'm not a Michigan politician that needs to get gamer Johnny out of my basement and on to a cushy non-profit no-show kickback job, courtesy of whatever big tech outfit wants a data center.
- > Quiet red areas rolling over to Flock
What is funding all those Flock reps jetting around BFE to dazzle and kickback the boomer city managers and county commissioners of deep red littleville America? Is it the 2 cameras in Big Rapids MI or the 2425[1] cameras in Detroit metro?
The "roll over" that mattered has already been secured.
- > Does it apply to completely novel tasks? No, that would be magic.
Are there novel tasks? Inside the limits of physics, tasks are finite, and most of them are pointless. One can certainly entertain tasks that transcend physics, but that isn't necessary if one merely wants an immortal and indomitable electronic god.
- "Perl6/Raku killed Perl."
Perl was effectively "dead" before Perl 6 existed. I was there. I bought the books, wrote the code, hung out in #perl and followed the progress. I remember when Perl 6 was announced. I remember barely caring by that time, and I perceived that I was hardly alone. Everyone had moved on by then. At best, Perl 6 was seen as maybe Perl making a "come back."
Java, and (by extension) Windows, killed Perl.
Java promised portability. Java had a workable cross-platform GUI story (Swing). Java had a web story with JSP, Tomcat, Java applets, etc. Java had a plausible embedded and mobile story. Java wasn't wedded to the UNIX model, and at the time, Java's Windows implementation was as least as good as its non-Windows implementations, if not better. Java also had a development budget, a marketing budget, and the explicit blessing of several big tech giants of the time.
In the late 90's and early 2000's, Java just sucked the life out of almost everything else that wasn't a "systems" or legacy big-iron language. Perl was just another casualty of Java. Many of the things that mattered back then either seem silly today or have been solved with things other than Java, but at the time they were very compelling.
Could Perl have been saved? Maybe. The claims that Perl is difficult to learn or "write only" aren't true: Perl isn't the least bit difficult. Nearly every Perl programmer on Earth is self-taught, the documentation is excellent and Google has been able to answer any basic Perl question one might have for decades now. If Perl had somehow bent itself enough to make Windows a first-class platform, it would have helped a lot. If Perl had provided a low friction, batteries-included de facto standard web template and server integration solution, it would have helped a lot as well. If Perl had a serious cross-platform GUI story, that would helped a lot.
To the extent that the Perl "community" was somehow incapable of these things, we can call the death of Perl a phenomena of "culture." I, however, attribute the fall of Perl to the more mundane reason that Perl had no business model and no business advocates.
- "not to debug any problems with it"
K3s is just a repackaged, simplified k8s distro. You get the same behavior and the same tools as you have any time you operate an on-premises k8s cluster, and these, in my experience, are somewhere between good and excellent. So I can't imagine what you have in mind here.
"It's still essentially adding few hundred thousand lines of code into your infrastructure"
Sure. And they're all there for a reason: it's what one needs to orchestrate containers via an API, as revealed by a vast horde of users and years of refinement.
- "I keep seeing teams reach for K8s when they really just need to run a bunch of containers across a few machines"
Since k8s is very effective at running a bunch of containers across a few machines, it would appear to be exactly the correct thing to reach for. At this point, running a small k8s operation, with k3s or similar, has become so easy that I can't find a rational reason to look elsewhere for container "orchestration".
- Merely an anecdote: I had one female house cat that clearly understood a number of words. She could easily and consistently pick out "catnip" in a sentence. "Cow", "get up", "tuna" and several other words and phrases were all understood.
This is unique in my personal experience. I've haven't seen this in other cats.
- "didn't support object tagging"
Thanks for pointing that out.
- "NAT instances"
That's what you did before AWS had the "NAT Gateway" managed service. It's literally called "NAT Instance" in current AWS documentation, and you can implement it in any way you wish. Of course, you don't have to limit yourself to iptables/nftables etc. OPNsense is a great way to do a NAT instance.
- I downplayed there, because occasionally I try to moderate my extreme cynicism.
It would be miraculous, in the biblical sense of the word. Not only because it would be a technical and regulatory triumph for RR and the UK, but because it would mean this is something other than what it appears to be to me.
None of this will get built. It's all fake, and after the benefits are taken, and the subsidy budgets are drained, and the various political and academic and regulatory folks have populated the requisite non-profit no-show jobs, and the professional opposition leaders have collected all the anti-nook bucks, and RR et al. have wiggled out of whatever obligations they're pretending to pursue via the holes they've already carefully arranged for themselves, these papers and headlines will be forgotten.
- If the differential in pre-war shell stockpiles and on-going shell production mattered as much as some people appear to think, Putin would be in Lviv by now, making deals with obsequious European leaders.
That hasn't happened. So what can be said? Perhaps that tube ammo isn't all that relevant a metric for military power any longer.
Arbitrary name+value pairs attached to S3 objects and buckets, and readily available via the S3 API. Metadata, basically. AWS has some tie-ins with permissions and other features, but tags can be used for any purpose. You might encode video multiple times at different bitrates, and store the rate in a tag on each object, for example. Tags are an affordance used by many applications for countless purposes.