Now that's what a backbone looks like.

Had an instance with almost 2TB on disk in 2015, it's probably a lot more by now, if it's still running as-is. Was for analytics/data-warehousing. Though the big table was partitioned so queries were always nice and snappy. The machine had 128gb ram back then, but probably never needed that much. The applications working with the data ran on that same server, so processing latency was usually <10ms even for larger queries.

10-15W for a wifi router with a cable modem, less if it's only wifi, but that's the general ballpark (this is measured with a calibrated smart-plug)

In my experience of almost a decade in infosec now, no, we're not okay. I don't know any other group where so many people are struggling with burnout or who have developed a drinking habit because of their jobs. Might be selection bias, but this industry eats people alive, more so than others.

I hope they'll try to upstream some of those drivers at least. I've written driver code for some parts before and I was better off not even looking at their code and only going by the datasheet. Except when the code worked around silicon bugs not mentioned in the errata. Fun times.

The goal is to always upstream every driver (and we do a pretty good job at that). Depending on the lineage of the software (who developed it, what they developed it for) - it may not be possible to meet the kernel coding guidelines - so we don't send those upstream.

Disclaimer - I work at ADI.

Most of the drivers in that list are already upstreamed.

that's interesting, ADI doesn't even list it anymore on their website but it's marked as still active. i guess it's still used in some test&measurement equipment.

they didn't though. zstd has been around even before the main dev joined fb, i distinctly remember it being under the persons personal github name.

you might've mistaken it for v which has been open-sourced in the meantime: https://github.com/vlang/v

Is it still full of impossible promises that strangely enough always get postponed or silently removed from the webpage?

Right, that's the one thank you :D

Most of the developers have been and still are in Estonia. It would be easier to enforce regulations there technically.

Exagear is originally from the Russian company Eltechs and was targeted to running x86 apps on SBCs like the Raspberry Pi. e.g. they provided Ubuntu images with wine to run windows apps on a Pi.

They discontinued the product beginning of 2019 and presumably? got bought by Huawei.

And since then the product changed a lot. They target Arm 64-bit machines only nowadays and support both x86 32-bit _and_ 64-bit application compatibility.