k_roy

> My point is that it doesn't save battery so turning it off is a wasted exercise.

Every watt matters, and turning it off hurts nothing I care about.

And apps DO change their behavior. The on screen keyboard pops up when the screen on a KVM connects before the keyboard.

Why the hostility? I’m not going to touch my screen anyway to try to avoid making it filthy.

I turn it off in the bios.

1. Takes extra battery 2. I’m not touching my screen regardless. It gets dirty enough

My last three or four laptops, which never even booted Windows, have had disabled touchscreens

And they can revoke that whenever they want

Awesome. Love to see it!

This is just the answer I was looking for. I definitely don’t know anything about the audio space, but am into networking hardcode.

I love seeing audiophile projects that don’t involve a rebranded tp-link switch and marked up 1000%

Riiip…. I hate private projects pooping on public spaces.

But it’s matching AND exceeding the performance of a $999 PCIe card designed for a similar purpose.

I would love to know why this is hand-wavy and not very cool? Even as not-audiophile, I’ve got ideas of things to use this for.

> RME HDSPe AIO Pro PCIe

> eth68 matches the latency performance of the RME card at 48 kHz and surpasses it by 0.33 ms at 96 kHz.

Okay, so first.

Using Mac is a no-go. For me, they became insufferably power-user hostile over the years.

Second,

God the safari rendering was so horrible for so many years. As a web developer, you have to target your greatest demographic, and Safari just broke everything more often than not.

Finally, even using Mac on enterprise, Chrome use is required because of the profile controls that can be exerted. And items #1/2 don’t help

I am not disagreeing at all. Nor am I trying to claim this behavior is safe.

I’m just pointing out the level-set that I’m sure the first time someone installs docker and tries to use it, chances are they are just going to install themselves in the docker group without considering the impact and continue on their day.

Default configuration or not, I also imagine the first thing people using docker do is to add themselves to the docker group via sudo.

If you are security-conscious, you shouldn’t be using docker anyway.

> The source was quickly identified, and it's trivial to avoid the tainted supplier.

The mixed messaging certainly didn’t help.

One day it’s Taylor Farms and the next the FDA was apologizing.

And even once it was found to be Taylor Farms, you can’t control every Taco Bell or anything else.

Mostly it just killed any consumer confidence in greens

And here I think you are just making up numbers.

I’m not claiming it’s good/bad one way or the other, but it’s the reality in which we live.

I’m just saying it’s weird to call AI okay for some things, like finding the exploit, but using that same AI is somehow the line in the sand when it comes to the documentation

Seems kind of subjective innit?

That world can’t exist unfortunately, because the minute someone wants a feature that isn’t in your core libraries, you just create a new library and we’re back to now.

You were specifically complaining about Opus’ nauseating style of prose, by calling out a sentence by the author you didn’t immediately comprehend?

>> I also ruled out the back doors: one USB interface, one LUN, both claimed.

>What the fuck does this sentence even mean? Opus’ tone and style is nauseating.

Seems pretty clear to me.

Nothing exposed beyond the expected surface.

Whining about everything being AI, is worse than the AI itself. Especially when the blog post as a whole is clearly human written. OVERWHELMINGLY so

The actual AI stuff in the article is clearly called out and delineated.