tobz

Hadn't heard of Fabworks until today. Testing out a quote on some parts I was looking at getting from OSH Cut, they're actually much better on pricing _and_ have more capabilities. (!)

Have you used them a lot? Curious what your experience with them is if you're willing to share.

If it's all sheet metal-esque pieces, where you could suffice with just laser cut features and/or simple bends.. then you should take a look at OSH Cut.

They have a fairly powerful platform -- instant quoting from uploaded design files, 2D/3D views, DFM feedback, good turnaround times, etc -- and the pricing isn't half bad for prototyping... but might not be as good for large-scale runs compared to bigger shops where you can nail down volume pricing discounts.

Regarding safety, do you have any links around the test results for the Kioma, or other car seats? You've mentioned a lot about the safety scores/test results in comparison to other car seats, but I couldn't seem to find a single mention of that stuff on the website? I also tried to see if something like Consumer Reports had a review of a Kioma car seat (either the current one or the carbon fiber one) but they had nothing.

One crucial difference I was able to spot is that Demikernel seems to have an approach that can work for OSes other than Linux. To wit, examples of the performance of the Demikernel approach are shown on a Windows system running in Azure.

Of the three examples you listed, none of them seem to support their kernel bypass capabilities in anything other than Linux.

Doesn't seem very productive to speak on behalf of two folks who you clearly don't have the authority to speak on behalf of. ¯\_(ツ)_/¯

Agreed.

Others have mentioned that the article calls out ignoring traditional in-memory cache daemons because of the additional network time, but with a targeted p50 response time (of their HTTP service fronting all of this), and caches like Redis and memcached being able to respond in hundreds of microseconds... it does feel like they didn't actually run the numbers.

The other natural alternative would simply be to run Redis/memcached and colocate this HTTP service on the same box. Now your "network latency" component is almost entirely negligible, and you've deferred the work of managing memory to applications _designed_ around doing so.

This.

We need more community/company interaction in Rust, especially in the networking space, instead of parallel implementations.

Heh, this is funny... I worked on an emulator for Dark Age of Camelot _and_ an emulator for World of Warcraft (WCell) and attribute experience from both projects to getting my first software gig.

I also remember (fondly) going through RunUO with .NET Reflector to pick up tips and tricks. :)

Sidenote: not that I think you are personally attacking them, but BuzzFeed does have some quality investigative journalism.

Listicles and clickbait help pay the bills, and I didn't believe it when I was informed the first time, but... it exists. Probably wouldn't be able to continue without the clickbait ad revenue, though, heh. :P