People - usually suit-wearers - have been making this spurious claim for decades, but it doesn't hold water.
The largest of the finest print reminding you that it's 'sold as is' (or more encompassing variants that might continue '... with no warranty for fitness of purpose') means that liability remains in the lap of the purchaser / consumer / operator.
(This has been a source of immense frustration over my career - where such people have assured me that they have 'recourse' (it's always vaguely described) by spending money on proprietary products & services, rather than opting for functionally equivalent or superior free options.)
I think your third paragraph is implying a distinction (or conflating the difference?) between LLMaaS's and self-hosting publicly available models.
If it's just where it's hosted that provides the legal insulation then things like OpenRouter would give you that. (But again, I suggest that it would not.)
If a frontier lab is willing to draft an SLA that assumes liability, corporate will pay for it as long as the cost/benefit is in favor of it over insourcing.
Sure, but that's quite a fanciful universe you're imagining there - the feasibility of a corporation obtaining insurance to cover that offer of liability ownership has got to be close to zero.
Peter Zeihan did a 5m video [1] on this 10 days ago (give or take) - and the history of how they've been used, and why the original design (big draw-downs during major emergencies - perhaps 5 of them, ever) hasn't lent itself well to the way they ended up being used.
The title is 'for single node local S3' but what they actually mean is 'for minio-compatibility', which is an entirely different question.
When I abandoned minio a year or so ago, I also surveyed the options, and settled on Garage. It lacked the GUI, but felt about the same complexity as minio. Perhaps a smidge more complexity, as I moved to 3-node and 5-node separate instances of garage, running as containers under Nomad.
I don't recall it being onerous, but I was looking for some basic S3-alike capabilities, not just minio-alike.
(How many people set out to build an object storage system with some number of AWS S3 primitives, but primarily try to match a third-party proprietary system's foibles?)
> So, Garage does work, but gosh…it is not just a drop-in replacement in terms of code changes.
I think in terms of actual code that uses local S3, it pretty much was a drop-in replacement. (I have multiple distribution/registry, Grafana Loki / Mimir, influx3 - all backing onto my object storage system, and the config changes there were modest - key+secret, and url - just as you'd expect.)
Yeah, whilst I probably wouldn't go that far I take your point. I suppose the difference is in how people respond to the way games dress up their mechanisms and how interesting they find the decisions around the processes they perform.
> VMware to Proxmox migrations are not affected ...
Amusingly - and acknowledging tiny scale and modest automation requirements of home lab compared to enterprise - as I started migrating to Proxmox a year or two ago, the process of shuffling VMs off my ESXi servers and onto Proxmox was surprisingly painless. Effectively mount the ESXi as storage systems, and then 'copy to here'.
IIRC the only small challenges were a conservative choice on target VM's CPU type (Proxmox seems to dislike defaulting to 'host' CPU) and the network / SCSI controller defaults. I assume designed to prioritise robustness over performance.
Proxmox been great for decades. I used it back in 2011 when I was sysadmin for https://sahanafoundation.org/eden/ - we had multiple live instance running for the site, wiki, translation, GIS. Just when kvm was getting support too (not openvz) so it was nice an snappy running on some donated poweredge 2950's (thanks zen.co.uk!)
Deployed for Haiti, Chengdu etc. All ran perfectly.
I saw some examples of this while travelling in Japan last year, and am keen to replicate. I suspect, like a lot of things, the local product there is superior to what I could find back home here in AU.
At some castle courtyard, we were walking around on a smooth-white-gravel surface, and I didn't immediately register how different it felt.
Stare at the ground for a few moments, and notice some of the small (15-20mm) off-white pebbles are perfectly aligned on a grid pattern.
Squat down to investigate, and they've got these corners of the plastic mesh geogrid topped off with little white caps that are almost indiscernible from the rounded white aggregate they're using as infill. It was almost like seeing a random dot stereogram, except completely regular (and no dinosaurs) of course.
The math is pretty interesting, and TFA didn't touch on this aspect I don't think. I'm looking to use 10-20mm irregular shaped scoria on a large-ish area, and the heuristic evidently is that your maximum aggregate size should not exceed one third of the geocell depth - so I'd want 50mm depth at most there, sitting on solid-ish sub-layer.
(I believe that heuristic goes out the window if you've got regular shaped gravel.)
The other ratio to consider is aggregate size to cell size, and that, in turn, is dependent on load and slope. Then there's the mechanical attributes of your in-fill (will it slowly crush over time, with expected loads - for softer rocks you'll definitely need a geotextile above your sub-base and below your geo-cell.) All tremendously more complicated than the 'few wheelbarrows of blue metal' I grew up with.
The sad part is how expensive it is (I’m in Australia too). Seems up front like a cheaper alternative to pavers but both the moulded plastic and the soft plastic that fans out versions are a solid $40-$45/sqm AUD.
Can buy brick pavers for that and you still have to purchase the pebbles to go in it…
brick pavers need a tamped gravel base, then bedding sand, and then polymeric sand to lock them together. the cost of install is not just the cost of pavers. and installation is something that requires enough skill that it's possible to do it wrong. depending on how much weight you plan to drive over it, you might also need to pour a concrete base for them.
geogrid is orders of magnitude easier and quicker to install.
Pavers for $40-45 - are going to be pretty unattractive grey concrete (well, cement) ones, right?
Even Bunnings (albeit marketplace) has 100mm geogrid for $20 / square metre.
Most local vendors have 'call us for pricing', but I've found a few others in the $10-20 range. Obviously, yes, in-fill on top of that - say $250 a cube depending on your tastes, so add $12-25 per square metre.
As per sibling comment - with some fabric underneath, and a modest amount of ground prep, installation of this stuff sounds fast and easy.
I don't use gcc directly - not in a long while - but almost everything I rely on uses it, and it's hugely encouraging to have the stewards of this project contemplate, and then determine to have this policy.
Meanwhile, I don't know who quotemstr is, but they don't sound sane in any of the exchanges in this thread.
How is this encouraging? They're sticking their heads in the sand and dooming themselves to irrelevance. All but the most strongly and wrongly ideologically motivated will contribute to other projects like LLVM when GCC asks them to code with rocks and sticks instead of taking advantage of arguably the most important invention in human history.
It's an invention that can invent things on its own, improve itself, do research, etc. The importance of such a thing should be obvious. The hockey stick that's coming for human progress overall is going to make the industrial revolution look like a flatline.
More important than the invention of writing, the printing press, electricity, the computer or the internet?
> The hockey stick that's coming for human progress overall is going to make the industrial revolution look like a flatline.
So far the effect on human progress has been pretty modest, I dare say. At the moment I would even regard it as a net negative on society. Maybe let's wait a few years before making such grand assessments.
Before 2020, vaccines referred to things like attenuated viruses - you were basically being given a small weakened dose of the actual pathogen to prime your immune system. mRNA shots are a different animal and they are quite new.
Far be it from me to doubt a stranger on the Internet, but can you point out any medical textbook or dictionary written pre-2020 that limits the definition of "vaccine" to "attenuated viruses"?
Amusingly, propagate has a horticultural, and non-horticultural meaning, and it's not obvious which one you're using there, because the bee's role is long over by the time the seed is ready to go out into the world.
Pollen can be carried (as noted by sibling and you) by lots of different insects, and there's myriad solitary and other (by conventional standards) weird bee species around, plus lots of plants are happy to pollinate themselves (tomato is a good example) or rely on wind (corn/maize is the famous example there).
When the common honeybee landed in the continental USA, about four centuries ago, the same people also brought in lots of (other) european plant species that had co-existed with Apis mellifera for millennia.
Thanks for the detailed comment! I always heard that bees pollinate the vast majority of plants, so in the parent comment, I assumed incorrectly that the meaning was for bees in general being non native.
Yeah, there's a claim I've seen about 'every third mouthful of food' that humans eat needs honeybees, and that may well be true.
I'm in Australia, and we only got Varroa in 2022, and it was suppressed for about a year before a regrettable 'oh well' attitude overwhelmed us. The last couple of years has seen a breathtaking impact.
Anecdata - one of my five hives is still struggling on.
Australia's experience since 2022 had (I thought) laid to rest a lot of the 'It's not varroa that's the problem' claims from armchair analysts.
But yes, per my earlier point, lots of our tree crops require honeybees to be shipped in - just because of broadacre / monoculture style farming. Well, along with honey production being its own industry - so they need to follow the nectar, and change up the flavours a bit, but also some trees just don't produce useful amounts of nectar but absolutely require a lot of pollinators for a few weeks only (almonds / peaches I think fit this category).
The largest of the finest print reminding you that it's 'sold as is' (or more encompassing variants that might continue '... with no warranty for fitness of purpose') means that liability remains in the lap of the purchaser / consumer / operator.
(This has been a source of immense frustration over my career - where such people have assured me that they have 'recourse' (it's always vaguely described) by spending money on proprietary products & services, rather than opting for functionally equivalent or superior free options.)
I think your third paragraph is implying a distinction (or conflating the difference?) between LLMaaS's and self-hosting publicly available models.
If it's just where it's hosted that provides the legal insulation then things like OpenRouter would give you that. (But again, I suggest that it would not.)
reply