hannesfur

With that going on, it's hard to imagine there once was a time where the news paper publishers hat little to no signal on what actually sold news papers. Given that papers were only sold as a bundle of articles and most sold through subscribers, they pretty much had to guess. So they had a rough direction they knew their readers expected and they had some sparse feedback from the "letters to the editor" but you had to be really angry to follow through on writing a physical letter, getting a stamp and walk to the post box just to complain.

I would argue, that helped journalism because journalists probably assumed that their readers would hold them to the same standards they hold the writers of the other papers too.

We have a focus on more complex ICs as we see them most relevant for this task. In that area we have ~95% of all components that are active (not EOL & recommended for new designs). But we try to have a little bit of every category to make most projects possible. While we expand our database, you can use the external search agent which uses the internet to track down parts that are missing.

Having worked on libp2p‘s DHT (Double Hashing for rust-libp2p) for a bit two years ago, it’s really great to see that there are improvements. To get to CDN level speeds though on dense networks, I still see it as an architectural flaw to not somehow encode network topology into the PeerID / identity in the DHT. A start would be to use the five RIRs. If you want to be more sophisticated, and I spent a lot of time theorising about this, you could have a dezentrally governed anycast IP address of Geo DNS to bootstrap new peers into their neighbourhood and couple that into their DHT identity. But do you want to put BGP into the hands of a decentralised system? Could you even do it in the governance structure of the internet?

Btw when we were working on our project HyveOS, we used Batman-advs routing table to quickly (really really quick) bootstrap new peers into the system.

Ah… sometimes i really miss working on this.

It says 8 Arm Neoverse N2 cores in the blog post. So not directly ARM Cortex, derived from ARM Cortex-X3 but same family as NVIDIA Grace, Google Axion and AWS Graviton4.

Not across all features, but certainly in specific ones. There are more advanced WiFi 6 chips, more advanced Bluetooth chips and faster MCUs. But they are all separate chips or companion ICs.

From the EXIF we can infer that every setting was left at the default. No exposure comp, no contrast, no HSL, no lens correction and a linear tone curve. Just the default Adobe Color profile at 5400K.

That’s fair but when there is an async version of the driver or Hal available it should be pretty straightforward to port it to synchronous, right? Maybe Claude code can even do it with minimal supervision…

Edit: Replace blocking with synchronous

Maybe stuff has changed a lot in the last year but I didn’t experience that problem so far. For me it was the other way around mostly. Where did you encounter that?