__dev @ __dev @lemmy.world

Posts

0

Comments

79

Joined

2 yr. ago

If you factor calorie intake of the bike rider you need to do the same for other forms of transportation. And if you account for the amount of exercise people are supposed to get to stay healthy there's no additional calorie intake whatsoever.

I know you're talking about the current AI hype cycle, but it was a buzzword in the 60s and again in the 80s.

I don't see how that's related at all. Having deterministic builds only matters if you're building a binary from source, if you're working with some distributed binary you'll be applying the patch to identical binaries anyway. And if a new binary is distributed, that's going to be because something in the source was changed; deterministic builds will still give you a different binary if the source changes.

Binary patching is still common, both for getting around DRM and for software updates.

For a phone who's ethos is sustainability buying a 2nd device just for music is antithetical. When my FP3 eventually goes out of support I'll have to look elsewhere.

AMDGPU is open source: https://github.com/radeonopencompute/rock-kernel-driver/, it's also upstreamed into Linux. The firmware is a binary blob though.

My issue with automatics is that there's a lack of control. It's trying to be smart about changing gears and yet never ends up doing what I want. It's like the throttle is going over a bad internet connection.

Because there are no gears to switch I don't have that issue in electric cars, it even feels better than a manual: Smooth torque curve and instant throttle response.

This isn't the full picture of those statistics. 10097 games have Platinum or Gold on protondb, out of 11223 with any results at all. It's not that there's 60k games broken on Linux, it's that there just isn't any data on those.

The only correct thing to do here is to extrapolate from the data we have, which is around ~90% of games work on Linux. So it's more like 63 000 vs 70 000.

Completely agree with you. A book by default is not a reliable source, published or otherwise. It's the scientific studies it quotes that are.

You say that like Apple would have to put in a ton of work for that. Android can already run on iPhones. It's just an ARM computer. Project Sandcastle already exists. All they have to do is allow unlocking the bootloader just like they do on macs.

Most of the ebikes and motor scooters I've seen have removable batteries. Gogoro in India even has a battery swapping network for their scooters.

AVX-2 has been in pretty much every CPU since 2011. For AVX512 intel's been shipping that to consumers since Ice Lake 2019.

At least it's transparent and often doesn't require root, unlike say a debian package.

USB-PD 3.1 standardized EPR in 2021; it hasn't been draft for a while.

They’re handing out magic beans with the selling point being that they can’t take them away from you once you get them.

And that's not even true in any practical sense. If reddit decides that the token in your crypto wallet is invalid, then it'll stop working on reddit. And since they're the only issuer every possible use is going to be tied to reddit in some sense.

AptX and AptX LL are not the same thing. AptX has the same latency as LDAC and SBC: >200ms; whereas AptX LL is actually decent at ~30ms. AptX is supported by Windows out of the box, AptX LL is not.

From what I've seen this isn't true. Search for "Windows AptX LL" and you'll see dozens of ways you might install drivers that add support. The most common advice seems to be to buy a dongle that supports it.

AptX LL indeed has ~30ms of latency at the cost of bitrate, but last I checked it's not supported by Windows out of the box. It's also been generally dropped in favor of the higher latency AptX Adaptive due to requiring a dedicated wireless antenna. The default experience of Bluetooth is still >200ms of latency. Also 30ms is 4.2 frames at 140Hz.

A big difference is that Telephone/Internet providers are natural monopolies. Competing requires building duplicate infrastructure to every client and so that naturally results in local monopolies. This isn't the case for Amazon.

This is plainly false. Hash collisions aren't more likely for longer passwords and there's no guarantee there aren't collisions for inputs smaller than the hash size. The way secure hashing algorithms avoid collisions is by making them astronomically unlikely and that doesn't change for longer inputs.