floatboth

There's more to a computer than just the CPU ISA.

While this particular thread is about the GPU, there is indeed "something different" about the M1 otherwise too. It is quite the non-standard SoC: unlike basically everything else (other than early Broadcom RPi crap) it even uses a custom Apple interrupt controller instead of the ARM GICv2/3. Also a custom IOMMU "DART" and a bunch of other peripherals. Very unusual: NVMe exposed as a plain hardcoded MMIO device (not enumerated over PCIe).

> Windows

https://www.microsoft.com/en-us/p/heif-image-extensions/9pmm... + https://www.microsoft.com/en-us/p/hevc-video-extensions/9nmz...

> Linux

https://github.com/strukturag/libheif (includes gdk-pixbuf loader and nautilus thumbnailer)

h.265 also lives on in open source software other than browsers. VideoLAN has been ignoring the whole licensing disaster because "Neither French law nor European conventions recognize software as patentable" for ages :P

It would also be extremely confusing to support something with only hardware decoding. People running supported hardware would start saying things like "Firefox supports HEVC" which would sound plainly wrong to someone with unsupported hardware.

Lots of phones support relocking to a user provided key (OnePlus does for sure) but it's a less trusted state than locked to the vendor key, I don't think it counts as good enough for full SafetyNet

Not that new – WiGig has been used for VR (i.e. displays but head-mounted): https://www.vive.com/us/accessory/wireless-adapter/

That's great if you only use these drives on your big computers. Sadly if you do want a "universally" portable drive – usable on an Android phone and an iPad and whatnot – you're stuck with horrible basic filesystems like exfat :(

More importantly ZFS by design ensures that if you unplug early and lose the last few writes, you'll end up in an earlier consistent state.

> One cable doesn't do everything

Well, seems like because physics™ it's hard to do both 420W charging and 69Gbps data over the same cable. And also people want thinner and cheaper charging cables. It's still better to have a unified connector and different capability cables.

> most cables get it wrong to a dangerous degree

That was the case in the early days. These days it's getting hard to find bad cables.

> negotiation is more complex and expensive to implement as well, even if you're only doing a low-capability device

No need for negotiation in a low capability device. Two resistors. It's not rocket science. Raspberry Pi did screw up and use one resistor but they made that mistake so famous that everyone knows not to repeat it now.

Well, the argument is that versions not being speeds anymore is the problem and it would've been easier if they were. Like they are in Wi-Fi for example.

PCIe does this in hardware

I've heard it's more like a "complex proprietary MPLS style network layer that can carry PCIe and DP and whatnot".

They wouldn't be able to do daisy chaining if it was bare PCIe, but it does sound horrible.

So it's basically like PCIe now.

Heck, even if one can afford paying that extra, not buying overpriced nonsense is a good principle.

Who's we? :) And what are the controllers called?

Plenty of USB-C SSDs on the market are actually M.2 in a trenchcoat, e.g. the nice looking black and orange SanDisk: https://www.reddit.com/r/hardware/comments/9631os/sandisk_ex...

IIUC, NTRU is only "quantum proof" because there is no (publicly known) quantum algorithm for breaking it, while there is Shor's for everything discrete logarithm based (both RSA and elliptic curve anything).

Snapdragon 845 and 855 mainlining is going pretty well. e.g.:

https://fosdem.org/2022/schedule/event/mobile_kernel_snapdra...

An active connection but not an active system-wide network interface. The point of these tools is that the wireguard client is encapsulated together with the proxy in a simple user-mode process, with no integration into the host network stack.

I'm not talking about embedded, I'm talking about e.g. intentionally minimalist systems that have to be self-building, or systems that have to be built with a formally verified compiler (which does not exist for C++), or anything else like that.

I guess the ability to work in really restricted/minimal environments where you only have a simple C compiler like tcc, and nothing like LLVM. Or paranoid environments where you can only use CompCert. Something like that.

Kernel devs typically do use SMP to refer to multicore. Even Wikipedia says: "In the case of multi-core processors, the SMP architecture applies to the cores, treating them as separate processors."

Eventually 4k page size kernels will work too (but 16k has better performance)

The RAM packaging doesn't really matter much, Apple runs JEDEC spec memory timings anyway.

But it is impressive that they get high GPU performance with LPDDR. Consoles also use one big SoC and unified memory – but with GDDR memory!

The cleanup being tied to the width increase was the first problem. The new width still being a fixed one was the second.

SVE is SIMD actually done right – on the Arm side in the near future, everything from smartphones to massive HPC boxes will be covered by the same clean SIMD ISA.

That's if working from documentation. With independent FOSS driver development, the big deal is the reverse engineering.

The screws are long gone, to unlock you prove ownership by sitting for a few minutes pressing the power button when told.

Wiping the installation is very much expected. The security model includes protecting data, of course data has to be wiped when removing security. Data on disk is encrypted with a key stored in the security chip, which destroys the key when security settings are changed.

Android does the same for fastboot unlock.

What's the big deal? If you want to flash UEFI and use a custom OS, why would you want to preserve the ChromeOS partition?

The browser is provided for free. Selling search defaults/inclusions is by far the least intrusive way to make money to fund the development of the browser.

Three top single-player story action games: Prey (2017), Horizon Zero Dawn, and Control. Each of those three is a masterpiece of worldbuilding, a deep touching story, and has awesome feeling gameplay.

Gtk4 and QML sure do (QML still (?) uses SDFs, Gtk4 uses atlas textures like WebRender does). Older frameworks don't.