I don't blame them for using a different config language, k8s style YAML sucks, which is why half of the k8s ecosystem is tools to generate it for you. And I believe Agent and Alloy are meant to be installable outside k8s as well. I do think it would have been less confusing to just call this product Agent 3.0 instead of Alloy, but I'm not too concerned about naming decisions.
Wow, I wish I'd discovered this about 12 hours ago. I just built a new PC yesterday and started installing and configuring Silverblue today, and basically everything I spent this afternoon on is automated by this project. Getting VSCode devcontainers working with Silverblue + Distrobox in particular would have saved me some time. Since I'm not particularly invested in my Silverblue setup yet, I'm installing this now.
Tip from one that has been running Silverblue for years: VSCode or any other editor from flatpak is a noob trap.
Yeah, I know now it's much more usable because it now integrates my host-spawn (https://github.com/1player/host-spawn) tool, but the easiest setup is to have a toolbox/distrobox container for work and dev, where you install all your tools.
I have been using an Arch Linux container (that starts at boot) with emacs, nvim, the myriad of LSP tools that are only found in AUR, exported with `distrobox-export` so I can start them from my dock.
Flatpak is for everything else (even Steam), but dev tools, editors and any other package should be installed inside a regular pet container.
Bluefin comes with vscode and devcontainers set up out of the box, we don't recommend pet containers.
We found that people struggle with the pet toolbox pattern so we send them right to the devcontainer pattern. This is an area where we differ from Fedora. It should just come set up out of the box.
VSCode and Devcontainers work iff you want to use VSCode. Using Silverblue or Bluefin without toolbox or distrobox is setting yourself up for failure, because otherwise one will try to install everything through rpm-ostree and then complain that ostree is slow and stupid.
I don't see how one might struggle with learning how to use distrobox. Of course there's some learning curve, but if one wants a normal Linux they might as well use stock Fedora. All one needs is to create a terminal profile that launches `distrobox enter container`.
(I used to use bluefin until recently, when a regression on distrobox forced me back on Silverblue. I could not for the life of me force rpm-ostree to downgrade distrobox to 1.5.0 vs the 1.6.0 bluefin ships with; I reckon it's because bluefin is a container rather than an ostree commit, and downgrading packages is still unsupported)
We've held back versions of distrobox before, if you file an issue we can usually figure it out.
Though distrobox is bash so maybe running the older version in your home directory would have been a good bandaid in the meantime, maybe I should write that up as a tip?
This is how I feel about Vlad's statement on their Discord that he wants to provide email services. That strikes me as a big project in terms of both development and operations, somewhat contrary to their privacy focus, and not something that their users are asking for (on Discord, I'd say that most commenters said they were unlikely to use it any time soon, switching would be too much of a hassle). And while I subscribe to Kagi and love the search product, they're still a tiny company with no long term track record, and far from what I would feel comfortable trusting with my email, which IMO is much more sensitive than my search history. Meanwhile, although Kagi Search already reliably beats Google IMO, there's still a ton of stuff they could do to improve their main product.
I had similar reservations when I read the email discussion. I hope they aren't spreading themselves too thin.
I use Orion as my daily driver (because of the nested tree view), but Kagi Search is more important to me, and I don't want to see that go down under the weight of a bunch of distractions.
Completely agree with you that Kagi e-mail will be unnecessary, even though I trust them on privacy. There are already great e-mail providers, such as Fastmail. But it makes some sense for them to go for e-mail, since they're already hitting Google on search. They're basically going after Google where it's possible: search, web browser, e-mail. They can't go after Google on maps or video streaming, so they do what they can. I'd much rather they innovate and get ready for the future of the internet after AI has destroyed traditional discovery.
The reason people use Google Maps is because businesses provide them with their opening hours and users provide them with reviews, photos, etc. A small company like Kagi can never have that (unless they buy it from Google), so they can't really compete with GMaps. Apple could have a shot, if they weren't so arrogant.
The benefits described sound contradictory to me. If you're removing enough heat to reduce the likelihood of Yellowstone erupting, you're removing enough to reduce the power output of the plant. Perhaps there's way to balance those two outcomes, but I know that other geothermal plants have sucked their heat reservoirs dry over decades of use. I suppose you could do a better job of matching the rate of heat extraction of the rate of natural regeneration, but I imagine that would enormously reduce the potential output of the plant, and that's not an issue this paper addresses.
On the other hand, preventing Yellowstone from erupting would be a pretty good outcome by itself, and getting a few decades (centuries?) of free power in the exchange is just a bonus…
That's more correct, also I realize I just counted number of commits rather than lines added. Close enough though, not like anyone would make any decisions with this list right?
I'm reminded of George RR Martin's quote (spoken by Varys) that "Power resides where men believe it resides." Over time technology makes it easier for small numbers of people to control larger numbers, and eventually I expect AI to bring that principle to its logical conclusion, but for now, Varys's observation remains the foundation of modern society in most places.
So then, why did Stannis fail? He was too worried appearing powerful, preferring either Seaworth or Missandei to speak for him?
A Song of Ice and Fire is based upon simple observations about politics, yet I doubt ever increasing centralization or technology will lead to control over belief. I think the future will be powered by disagreements.
Orcas are almost certainly several different species as well, but they remain officially classified as one until scientists agree on how to divide them up.
I thought orcas were traditionally divided into three types. There is no standard for what is or isn't a "species".
But it doesn't matter at all; the difference between the taxonomic level of "sharks" and the taxonomic level of "orcas" is unimaginably large regardless of what you want to call the levels.
Not at all. Without even mentioning plants and bacteria, wolves are canis lupus and dogs are canis familiaris. But interfertility is often a bigger problem between two types of dog than it is between a dog and a wolf.
I've read that the the Hawaiian islands disrupted ocean swells in ways that Polynesians could detect even 1000+ miles away. In addition, the Hawaiian islands are huge and lush, and dumped a large amount of plant debris into the water, some of which Polynesian sailors would occasionally notice while at sea. I'm skeptical that those signs would have been noticable all the way from the Marquessas islands, but the Marquessas Polynesians were likely ranging 1000+ into the ocean themselves, which evidently was enough for them to deduce the existence of large islands in the general direction of Hawaii long before they discovered it. Evidently according to oral tradition, the discoverers of Hawaii arrived equipped with plants, animals and other gear to establish a new settlement- they knew the islands were there before anyone set foot on them.
It's the same for the settlement of NZ, they brought kūri, kūmara, uhi, and aute.
That's dogs (for hunting and food), sweet potatoes, yams, and paper mulberry, used to make tapa cloth in the Pacific.
(We're not sure if they didn't bring the pigs and chickens widespread in Polynesia, or if they didn't survive the voyage or the initial landings, or their bones didn't end up in excavated middens. Maybe a flu virus got in there?).
The aute didn't really flourish in Aotearoa, and the cloth derived from it wasn't that warm, so clothing as well as fish hook styles, canoe styles etc. from Polynesia were rapidly adapted, but it's clear that the Polynesian settlers who became the Māori, they came prepared.
Birds seem to have provided evidence of land too - migrating birds consistently appearing from one direction suggest that land could be in that direction.
Polynesians also seem to have taken birds on their voyages - when a bird is released and comes back there's no land nearby, if it flies off in one direction follow it to find land.
I assume these are all currently non-standard APIs that Firefox will nonetheless be expected to implement? Does Firefox ever force work on the Blink team, or it is it only ever the other way around?
Getting the features into the spec is the vast majority of the work. Though some features are not yet implemented in Firefox or Safari, they have both indicated their intention to do so.
The article should make that clear right at the start. I read the whole thing and came away with the strong impression that these things were Chrome-only (apart from the one mention of Firefox).
