This is astonishingly bad power usage for a laptop, a complete dealbreaker: "...early tests show that the SoC already draws about 16 watts at idle..."

For some context, my 12-core Intel laptop consumes 1.5 to 2 watts at idle for the SoC. Apple M silicon might consume even less.

yeah, that is impressively bad. Perhaps a reporting error and it is 16W at full tilt?

Maybe it's a typo and it's 1.6W.

> upgrade kit

> makes your laptop slower

Hmm...

This was a nice surprise when learning to code for NES, that I could write pretty much normal C and have it work on the 6502. A lot of tutorials warn you, "prepare for weird code" and this pretty much moots that.

Zig is so good at this, it is also probably the easiest way to cross-compile C.

And it could be used as drop in replacement for gcc/clang

https://andrewkelley.me/post/zig-cc-powerful-drop-in-replace...

I think this is _Alignas/alignas.

    struct foo {
        _Alignas(64) float x,y;
        _Alignas(64) int     z;
    };
    _Static_assert(sizeof(struct foo) == 192, "");

The example I linked uses alignas, but the key is knowing what value to pass. std::hardware_destructive_interference_size tells you what the current/target hardware's correct align value is, which is the challenge.

I very much used to agree with this, but some time this summer the ChatGPT iOS app started to change this for me. I have definitely had days where I've felt as coding-creative as I can be on a laptop but instead just texting my AI interns to handle the execution while I'm out for a walk.

I don't understand why this article invents and explains a phony ranged-float fix when the real fix from the footnotes would have been just as simple to explain. The deception needlessly undermines the main point of the article, which I completely agree with.

The real fix felt more complicated when I drafted this. Seems like it isn't; I'll think about updating the post

That fix has limited applicability. x * x is also a non-negative float. But abs(x * x) is not optimized. Or abs(abs(x)+1). GCC, for example, does know that.

You're not wrong that he wasn't physically fit, but he was also one of the most human people many of us in this thread have ever met.

For a good long while at least, this flag was a signal for the browser to use CPU rendering, because of the overhead of GPU setup for rendering very changing content was too high.

My knowledge is dated and second hand though. New GPU APIs hopefully changed this!

Do you have a citation? I don't believe that was ever the case when I worked on this.

I found this especially nice working with large SIMD constants.

Okay, I'll bite: 2 and 5 are prime, this is the perfect fifth problem, only approximate solutions are possible. Make me wrong!

Cut into 8. Give 1 piece each.

For the remaining 3, repeat this method.

Let epsilon be a number as small as you like...

The solution is to have a pet/toddler that makes even larger epsilons disappear.