Some of us would like our expensive hardware to work without hacked third party dongles.

All of us would like our expensive hardware to work without hacked third party dongles. But given that this isn't possible with AMD open source drivers at the present time, this is the best we'll get for now.

So we can also fly? Sign me up!

And echolocation! Time to form a queue.

> Teach Yourself to Echolocate A beginner’s guide to navigating with sound.

https://www.atlasobscura.com/articles/how-to-echolocate#

You can build docker images with nix, in which case you can have every dependency be its own layer.

That is clearly not what these people are doing, though.

Futurelock is not about cancellation safety (cancellation is actually one solution to futurelock), though the related issues that are linked in that post are.

At an early stage startup, shipping a feature should not require "many meetings across product, legal, and engineering". Especially not one that can be mostly built in a day.

Ethernet doesn't support 240 W.

I am very happy that I can charge my phone and laptop from the same charger, and don't ever have to worry about whether the cable I'm using will be a fire hazard.

PoE has been around for longer, and while it doesn't go that high (90W --- but at much longer distances), it uses passive cables just fine.

POE is an quite expensive thing to implement on a board. Flyback transformers are essentially required to support the standard.

At the cost of much higher complexity on each end. USB-C still supports completely passive old chargers and devices.

The cable can still be a fire hazard if it’s a cheap cable that lies about its rated wattage, no?

That goes for anything that lies about its rating though

Right but consumers are much more likely to buy a cheap USB charge cable that lies about its rating (via internal chip) than an Ethernet cable that lies about its rating on the package.

It doesn’t seem to be a huge problem with extension cords.

Do ethernet cables even specify a wattage?

I think the real issue here is that two Android phones take photos with incompatible naming schemes.

I am sure that at some point someone thought the milliseconds should or should not be separated from the seconds and made that change without thinking through the consequences.

zoxide stores a rank for each directory based on how often you visit it, but you can manually adjust the scores.

Run `zoxide query -ls thing` to see the scores, and `zoxide add thing -s AMOUNT` to increase the score.

That's good to know, when I needed to raise the score for a directory I just did a bunch of `cd .`

(⌐■_■)

If xkcd took comment form, this would be it.

I don't think that's true. I have seen R4L folks reiterate time and again that C changes are allowed to break Rust code, and they will be the ones to fix it.

I think they were saying they want a format instead of PDF where the reader can change those things.