But actual app does not matter, the main take away for me is: it is easy and fast to write bloatware (esp. with AI), but not that easy to distill to what is really needed. And what looked like a weekend project, a couple of hours max (with help of AI), now lingers for 2+ weeks on-and-off on evenings (of manual effort).

[*] like these https://www.jbctools.com/cartridges-category-4-design-Spoon-...

And thanks for pointing at CWDM4, these are quite cheap on ebay now

Where did you get "several ms of latency" figure from? I have not measured external card, but may be I should do it... Because cards themselves have latency in range of microseconds, not millis.

Which cards do you prefer for 100G, and what is the situation with dacs/optics?

Really: because I can, and it is fun. I upgraded my home lan to 10G, because used 10G hardware is cheap (and now 25G enters the same price range).

Pic of a previous cx3 (10 gig on tb3) setup: https://habrastorage.org/r/w780/getpro/habr/upload_files/d3c...

10gig can saturate full speed, 25G in my experience rarely reaches same 20G as the author observed.

> Don’t display an icon if you can’t find one that clearly represents the menu item

> Not all menu items need an icon. Be careful when adding icons for custom menu items to avoid confusion with other existing actions, and don’t add icons just for the sake of ornamentation.

> Instead of adding individual icons for each action, or reusing the same icon for all of them, establish a common theme with the symbol for the first item and rely on the menu item text to keep the remaining items distinct

IMO, both articles fail to deliver on their titles :(

Both fail to list really cool parts, and both reiterate same arguments several times. This one even looks like an LLM output, but I'm not sure.

The part of NICs address space is mapped to a process (control registers and memory rings), and whole driver just runs in your process without going through the kernel. Of course, it ignores usual stuff like firewalls, iptables, etc, but who cares when all you need is the lowest latency possible )

How about “not breaking stuff” which can not be upgraded? Like old sites/services without active maintainers but still useful. Or hardware appliances that still work, but will not get firmware update ever. Let alone rss feeds, brought up multiple times in the linked thread.

Looks like builtin polyfill (similar to pdfjs in FF) would do. But google seems to be reluctant doing it.

Edit: answering myself, this seems to be (at least partially) merged into the dotnet itself https://github.com/dotnet/runtime/pull/102655