This is before the DOM Canvas 2D API existed, so effects like digging are implemented by overlaying multiple 1px-high black GIF <img> tags over the background.
For a single CPU:
844 GB/s memory bandwidth (12 channels of DDR5 RDIMM, 8800MT/s). 4.3-6 TFLOPS.
Basically comparable to a modern (although not top-end) GPU, so good for HPC & AI workloads. (though only 2 CPUs per node, with GPUs 4-8 is more common)
For anyone not familiar with Fujitsu's CPUs, worth noting their overall long history with HPC, and more recently, ARM. FugakuNEXT is "NEXT" because the current Fugaku (#1 on TOP500 for a time, and still in the top 10) also used an ARM CPU from Fujitsu.
Benchmarks will be interesting to see but I doubt the cores alone will be able to reach beyond ~500GB/s of BW, and even if they match that figure it will be great.
Man this looks amazing, more competition is always welcome! The issue for Ai inference is always firmware/software support. Up until recently, that rocm hardware became usable, let alone optimized. Nvidia had a big start, now everyone is trying to catch up
You're just offering non-helpful ivory tower criticism without even understanding the problem space (which is actually one of the hardest open research problems in software engineering, cs.PL + formal methods).
But if I'm wrong, dare say, how would you write a production memory-safe JIT compiler today?
If I couldn't guarantee memory safety, I wouldn't. We're talking about an optional feature for JavaScript engines.
Security is where the rubber hits the road. It's whether customers' identities get stolen. It's whether leaders of undemocratic countries can monitor communications, locations, and social networks of people whom they oppress.
Calling this an "ivory tower" criticism is, ironically, a lack of acknowledgement of reality and that our actions have consequences to others.
This is only applicable to die photographs of the silicon layer.
For CT scans, which use X-rays, the visible structure is very likely due to the metallic (copper) interconnect, clock- and power-delivery layers, which are generally quite different from the underlying transistors.
These layers are larger-scale, and copper also absorbs X-rays much more strongly than silicon.
I think you overestimate the amount of senior engineers... even at the extreme end of top-tier big tech, only around 30% can be considered senior. Staff engineers who regularly think at the level GP talks about are 5-10%.
Everywhere else the percentages are quite a bit lower still (if judged by the same standards).
Ya I was very hand wavy. Though in my experience a lot of smaller shops have a higher percent of seniors than big tech. And I don’t know how much smaller shops there are, so I rounded up. Also smaller shops depend more on this well rounded thinking.
No... Adaptive sampling is a family of statistical methods to choose an appropriate decimation strategy for arbitrary events based on real-world occurrence distributions.
It can be applied to tracing, metrics, logging ("sampling") and profiling.
Trick: it's easy to check this - just try eg. a specific short almost-nonsense high-entropy phrase such as "Scarf Color Plump 蘼撅" via OpenRouter using the playground for different providers/models, and observe the shape and language of the reasoning and the response, which tend to be quite different (MiMo and GLM are quite similar, but still identifiably different enough).
(as I and others have mentioned in the thread): The attacker can just move the malicious code from build.rs to lib.rs (ie. build-time -> test/execution-time).
Then the problem is the language, as the grandparent observes.
This is before the DOM Canvas 2D API existed, so effects like digging are implemented by overlaying multiple 1px-high black GIF <img> tags over the background.
reply