I wanted to visualize this, so:

     ┌────────────────────────────────────────┐ 
   6 │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡜⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡜⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢰⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⠇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡜⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⠜⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢠⠊⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡰⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣀⡠⠤⠒⠊⠉⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     │⠀⠀⠀⠀⠀⠀⠀⠀⠀⣀⡠⠤⠔⠒⠉⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
   1 │⠀⠀⣀⣀⠤⠔⠒⠊⠉⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀│ 
     └────────────────────────────────────────┘ 
     2010                                  2030

It’s not precise; I took the text

After getting to 1% in approximately 2011, it took about a decade to double that to 2%. The jump from 2% to 3% took just over two years, and 3% to 4% took less than a year

and converted it to:

2011,1
2021,2
2023,3
2024,4
2025,6

Since my mobile client renders the terminal output poorly,

Proof that Linux use is rising asymptotically, and there will be infinity Linux users by 2030.

It’s not a dependency, though. I mean, it could be, but you can just ssd easily rewrite or copy/paste; his repos is basically a single for with a half dozen functions. It’s a hundred LOC, or something. Copy the file, change the package. A little copying.

I usually just re-implement the asserts as I need them, but copying this one for over into your project introduces no dependencies. If you import testify, you now have dependencies on

• testify
• github.com/davecgh/go-spew
• github.com/pmezard/go-difflib
• github.com/stretchr/objx
• gopkg.in/yaml.v3

because that’s what testify imports.

It’s not the same, at all.

Messing around is how blow jobs were first invented. If we’re ever going to discover the next major sex move, we’re all going to have to do our parts and mess around a lot while we’re cleaning the starfish.

Remember:

Promote a Kim,
And the future is grim.

I’m lucky to know I’m a smart dumb person, because

1. I know several, and have encountered many, truly smart people.
2. I’ve known a great many clever dumb people.
3. I know my father, and believe genetics is a strong influencer (not determiner).

For many cases, writing assert is both trivial and effective, and prevents importing yet another fairly large dependency.

A little copying is better than a little dependency.

• Rob Pike

As the article (discovers?) Go does not, and has closed the discussion on, implementing TCO as “will not do.”

I’m a little angry at the Go developer community for endlessly harping on Generics and letting TCO languish (the latter which led to this decision); it doesn’t reflect well on the sophistication of the community.

Fantastic! I used EMACS for 3 years, vi(m) for 22, Kakoune for 2, and Helix for the past 3, and Helix is by far the best. I think it benefits from having arrived just in time for TreeSitter and LSP to be mature, and learned a lot from vim and Kakoune.

I like that it’s modal, consistent, and fast.

Some particularly exciting changes in this release:

• DAP integration
• New, more capable, file explorer (the old file explorer is pretty basic)
• command-mode expansions (%{language}, and %sh{...})!
• purported improvement in command expansion (hopefully pipe and exec expansions are better)

Glad to see it!

This is a fantastic project, BTW. I’ve been using it for a ton of stuff for years and have never had a reliability issue. Multi-platform, even Android has a (third party) client (DroidFS).

This is the best hot take.

Give me the accent. It’s more interesting, and less annoying. They get practice, I get to listen to an actual human.

There were countless spin-offs, but I think this is the original.

This.

It’s a choice.

I almost never use web apps; I do only when what I’m doing is fundamentally a web interaction: banking, for instance. Everything’s on their servers anyway.

For everything else, I (too) use shell applications. Even if I didn’t, there are tons of native GUI applications to choose from, and they are often far better experiences than SPAs or Electron apps: just look at the memory and CPU use, if you want a baseline metric.

Why do people do this? Because they fancy that they’re providing a good enough interface that works on every OS. Which is often not the case, and by the time you invest enough effort to get your SPA working well on every possible platform you could have written native apps that look and function better; and most organizations still throw in the towel and add a caveat “works best in X”, giving lie to the “web apps work everywhere.” So: laziness, or being cheap, and not really carrying about the user experience: those are the reasons people write web apps.

I think the laptop really does matter, and it’s because chipsets are not all equal in how well their sleep modes are supported in the OS.

I’ve been buying XPS13s for over a decade; I’ve had four (three personal, and one requisitioned for me by my job), and sleep and suspend have worked almost flawlessly on them under Linux. In the office, most everyone else would move between meetings or to their desks with the lids almost closed, to prevent sleep and the problems it caused, but I’d just fearlessly close my lid; it was ironic to me that running Linux on the XPS I had more reliable sleep behavior than the Windows people on their laptops.

For OP: low power, initialization, and restoring state has to be implemented by each chip, and there are a lot of shitty, poorly implemented chips. Then the OS also has to store and restore state for each chipset, and even if the chip implements it well, the OS has to do a good job restoring power in the correct order and restoring the state for each chip. If anything goes wrong in either the chip or driver implementation, you get a broken state.

This is aggravated by the fact that Linux is a monolithic kernel, and if any device drivers get borked it usually borks the whole kernel. This wouldn’t be as bad a problem if Linux were a microkernel architecture and drivers could just be killed and restarted.

The package archnews2 also provides an arch news reader. This issue was also announced in Arch forums before it was rolled out - I saw it in Lemmy.

But, yeah, you really do have to read archnews release notes. Frankly, it annoys me a bit - pacman should have the concept of breaking changes and show related news before upgrades. I think one of the news packages (maybe archnews2?) has a config setting that always displays news before upgrades, but it’s only annoying because it is ignorant of whether the news item affects any given system, so it’s often just noise; I think I turned it off because it kept showing me the same news every time.

It’s the worst part of Arch, and it’s poorly handled. I don’t know of a rolling release that handles informing the user of, breaking changes better, though.

Do any of you know another solution to stream audio from my phone to my server

I use snapcast throughout my house and devices, but there’s no snap_server_ for Android.

I’ve been meaning to try roc, for which there is an Android client that will both play and serve.

Sonobus also claims to be many:many; I haven’t tried it either and it doesn’t look particularly active.

I don’t use UPnP or DLNA because of the security issues, so I can’t offer a suggestion about that. I thought DLNA was a pull oriented protocol - like, to send music from your phone you’d have to select and play on your computer with a DLNA client. Can you push media with DLNA?

Rust needs to be reduced back to ore, using a reactive, usually coke. Coke is purified coal. Coal is a fossil fuel. You can do it with charcoal, which can be made by burning wood, so it’s possible without coal, just not as efficient. This assumes you can gather the rust - it tends to break down and disperse into the environment, but if you broke up concrete to get at rusted rebar and could collect the rust, you could reduce it with charcoal.

Again, it’s a matter of scale. We mine iron and deposits because we can get large amounts in seams. If you’re trying to harvest rust and reduced it with charcoal, you’re producing iron on the scale of making knives and swords, not cars, or combine harvesters, or more rebar.

It’s a chicken-egg problem. We have been able to come as far as a have because oil, coal, and iron were just laying around on the surface, in huge quantities. Those are gone, and now you need the big tools first to get at the reserves that are left.

Any worked iron product rusts. If we’re talking about evolutionary time scales, any exposed metal - which is most of it - is going to be unusable within thousands of years, and even rebar embedded in concrete will be gone in millions. Heck, our concrete isn’t even as good as the Romans’, and even that’s going to break down in thousands of years.

We’ve stripped the raw, surface, easily accessible stuff and worked it into things that will degrade. There may be some scavenge, but nothing that can be gathered in any quantity to build an industrial society on. At best, future societies will be like medieval Japan, where iron is rare and steel precious and hoarded, only unlike Japan, there won’t be a future where they can import huge quantities of the stuff from China or Australia, because getting to the deposits now requires an industry and advanced mining equipment… which is all made out of iron they won’t have.

Gold will be interesting. Again, it’s not just laying around everywhere just under the surface. Instead, there will be isolated pockets of huge piles of the stuff. Gold doesn’t degrade, but it’s all hoarded. There’s a bunch in electronics, but in tiny, tiny amounts in each device; trying to salvage that is really hard, and yields trace amounts. No more nuggets the size of your thumb, or your fist. If a future civilization could build a global economy, then gold wouldn’t be an issue. Uranium will be hard, as will platinum, and platinum is a useful, but consumable, catalyst, and rare even today it’ll be almost unheard of in a perpetually pre-industrial post-apocalypse.

Fossil fuels are going to be the big issue, though. What’s left will simply be inaccessible, and without fossil fuels you don’t have plastics, industry, fertilizers at scale, global transportation, or the ability to work whatever metal you can find, at any scale.

It’s pretty nice, although IME it’s really crashy.

Thank you. I don’t know that I ever knew that statistic about Greenland’s population. The nuke statistic tossed around - that I always heard - was something like “there are enough nukes to blow up the world a million times,” with is a silly, sloppy metric that doesn’t day anything about the actual warhead count. Are those Tsar Bombas, or Fat Man? How many megatons are required to “blow up the world” once? But that graph is interesting; it’s even more interesting that there population of Greenland and the number of (viable) warheads on the planet have been so relatively close.