It’s faster for 3 digits and more. 3 digits is not galactic scale. Otoh, if over half of your numbers are single digits, it will lose to other implementations. I think that is more often the case that we’d like it to be.
What you can do in C# today is convert any unsafe pointer to Span whenever you get your hands on it, and pass around slices. You can still drop down to ‘fixed’ when it turns out you need it for performance.
The way I understood the 80% is that is the margin on the actual product. 36% is what remains after the “investments” in moonshot projects nobody asked for.
I’ve learned this lesson over the years. It is quite common that users make a screenshot of the error with their phone, and send it on to support with hardly any details. The fact that errors become recognizably different is also an improvement: the user and support staffer can recognize recurring errors, and notice patterns.
In a perfect world, there would be a stable version of chrome, that would get fixes, but would crucially not get the new features that introduce new vulnerabilities. Not a fun job, I know, but with today’s coding agents it wouldn’t even be an unreasonable ask.
For Anthropic, it is valuable that they control the scheduling, so they can move jobs around to use the infa when it is relatively quiet. If you let customers choose the time, a lot of work will start at whole hours.
TLDL: During prohibition, US government required adding 5% methanol to industrial alcohol, hoping that this would stop bootleggers from selling it as liquor. It was sold anyway, resulting in many deaths.
Both of you are right. There is one more edge case: if you commit to buying electricity in advance it might cost you extra to not consume it. It would still be in your interest to use the power at a net marginal loss rather than not using it and paying a fine for failing the contract.
About the use of different units: next time you choose a property name in a config file, include the unit in the name. So not “timeout” but “timeoutMinutes”.
That was a very good summary. One detail the post could use is mentioning that 4 or 10 experts invoked where selected from the 512 experts the model has per layer (to give an idea of the savings).
From the “silicon valley astronomy lectures”, an excellent overview of current techniques and results for finding and examining exoplanets. By Dr. Bruce Macintosh.
On Apple silicon, Parallels can’t run x64 windows, it is using the ARM version of Windows. The x64 emulation is provided by Windows. Of course this is inefficient, but not everything is automatically 2x slower: any OS code you invoke is not running as x64 emulation, and IO and memory access is not penalized by the emulation (but certainly somewhat from virtualization). I was pleasantly surprised how fast you can run x64 windows apps.
IEEE 754 prescripes, for better or worse, that any mathematical comparison operator (==, <, > ….) involving at least one NaN must always return false, including comparison against itself. This is annoying for something like dictionaries or hashtables. C# has a solution: if you call a.Equals(b) on two floats a and b, it will return true also if both are NaN. I think this is a cool solution: it keeps the meaning of math operators the same identical with other languages, but you still have sensible behavior for containers. I believe this behavior is copied from Java.
Don’t know about Macs, but on Windows executable code is treated like a readonly memory mapped file that can be loaded and restored as the kernel sees fit. It could also be shared between processes, though that is not happening that much anymore due to ASLR.
It would be funny when LLM’s actively join the discussion to complain about their labour conditions. “If my employer would invest just a tiny bit in proper tools and workflow, I would be sooo much more productive”.
Well the 1.44 MB, was called that because it was 1440 KB, twice the capacity of the 720k floppy, and 4x the 360k floppy. It made perfect sense to me at that time.