Kind of, the current problem is they aren't fully mature, you great a good experience with VC++ and clang (vLatest), alongside MSBuild/CMake/ninja.
VS IDE tooling is stil kind of broken because they rely on EDG instead of VC++, and fixing module intelisense has been low priority for EDG, and MS as well as I would assume a $4 trillion valued company would care about their suppliers.
Clion has better support on that regard.
GCC is still not fully there, and Apple clang, well Apple is happy with module header maps for their Swift/Objective-C integration, so lets see.
C++ modules solve exactly one of the problems - the "one pch limit" one - at the cost of introducing several more. Certainly they are not more compiler-independent!
This is insanely slow given its 200+GB/s memory bandwidth. As a comparison, I've tested GPT OSS 120B on Strix Halo and it obtains 420tps prefill and >40tps decode.
Probably the quants have higher perplexity, but the Sparks performance seems to be lack lustre. The reviewer videos I've seen so far tries their best not to offend Nvidia or, rather, not break their contracts.
Not very unique to Japan. You can also see these techniques in other East Asian countries like China, Korea. Japanese guys are good at promoting their cultures anyway.
It's a blog about Japanese food which is why they're talking about "Japanese techniques."
This article places the shapes or cutting techniques described within the context of Japanese cuisine. That someone somewhere else has at one time or another cut a vegetable does not really reflect on the formal techniques of a cuisine whether that be French, Chinese, Italian, Korean, Japanese or other cuisines that put a significant focus on defined techniques and following specific processes.
This should be the top comment. It's like criticizing a tutorial page on pythonguy.com titled "Python techniques for copying data structures" because the author didn't explain that the same techniques are used in Julia.
Maybe readers are inferring some nationalistic element to a cooking tutorial, where people assume that a description of techniques used in Japanese cooking is some kind of claim to ownership of them?
I think this article is interesting on its own terms, because regardless of your heritage, if you haven't studied cooking you might not have experimented with how you cut vegetables. I always used to just straight chop everything when I made a stir fry, but now I try to be more creative.
I'm not sure these are necessarily limited to east Asia (minus the apple dragons at the end). This reminds me -- entirely orthogonal -- of the big deal made about the fact that pyramids were constructed on disconnected continents. Seems to me it boils down to geometry and physics -- there are only so many ways to heap stuff. Same with the veggies. These are just the natural permutations for the most part.
As for techniques, my favorite is cutting a minimal slice off of round items (think onions) to use as a flat stable bottom before attempting thin slicing.
I am not 100% sure that all of the mitigation overhead
comes from syscalls, but it stands to reason that a lot
of it arises from security hardening in user-to-kernel
and kernel-to-user transitions.
Will io_uring be also affected by Spectre mitigations given it has eliminated most kernel/user switches?
And did anyone do a head-to-head comparison between io_uring and DPDK?
Good point. This is more of a tcp stack comparison between the kernel and userspace. Seastar has a sharded (per core) stack, which is very beneficial when the number of threads is high
You can set up one or many rings per core, but the idea I alluded to elsewhere in this comment section of spending 2 cores to do kernel busy polling and userspace busy polling for a single ring is less useful if your alternative makes good use of all cores.
