Decades ago they used to pull completely off the can (think Jimmy Buffet "stepped on a pop-top").
I should barely be listed as a co-author on what Claude does for me. Hiding Claude's contribution feels about as true as a combover to me.
That's kind of what reddit used to feel like when it was brand new. Can you believe it?
I have found qwen 3.8's coding quality using opencode to be similar to claude or gpt from 6-9 months ago, except much slower.
My rule of thumb is that integer ops cost 1 cycle except divides, floats 3 but maybe divide is a bit more, then integer divides are like infinity at 20+ cycles that cannot be amortized by vectorization. When you code…
They're typically like a 3-cycle op, right? Obviously that's not zero, but as far as floating point ops get it's a cheap as it gets, like an add, mul, fma, that sorta thing.
Don't forget SubEthaEdit! That was the first multiplayer editor I recall. Never found a use for this sort of thing once novelty wore off. :/
I don't think there is necessarily one ideal middle ground here. It still feels to me like what's best is a function that depends on who and when. I see it as something like a personal gradient descent. You're working…
Yeah it makes me sad too. It's a one-way veil, no going back once I experienced the new magic. Sometimes I pop back into a terminal, mkdir, git init, crack my knuckles to do some all-natural hacking and the sadness sets…
On about day 2 of using Fable I realized that the .vimrc I'd been maintaining for 15-20 years would probably never change again. With Opus I still feel like I'm pair coding and want to get in there and make some changes…
I have never seen Codex or Claude get manual memory management wrong. I used to be pretty fastidious about using leak sanitizer or other such tools to catch my own memory management issues, and while not quite useless,…
Part of that could be ABI constraints. There are some surprising calling convention differences between a vector and a struct or union with vectors in it, and they vary platform to platform. E.g. on ARM a struct with…
I hate to admit it, but the Corona "Change your Latitude" ads are what locked it in for me.
what I mean here about NaNs is that from a testing perspective, I want to be able to write a test that expects NaN in the same way that I write other expectations, and you can't do that with ==. assert(x == 7); // fine…
My preference in tests is a little different than just using IEEE 754 ==, _Bool equiv(float x, float y) { return (x <= y && y <= x) || (x != x && y != y); } which both handles NaNs sensibly (all NaNs are equivalent) and…
Yes, it's a "Brain float", basically an ordinary 32-bit float with the low 16 mantissa bits cut off. Exact same range as fp32, lower precision, and not the same as the other fp16, which has less exponent and more…
The closest term I know is "just-so story".
I am also not looking forward to the system transitioning from "big experiment, burn money to make it good" to "established business unit, tweak it to death for incrementally more money / personal promotion." We're…
If I remember correctly, the AVX2 feature set is a fairly direct upscale of SSE4.1 to 256 bit. Very few instructions even allowed interaction between the top and bottom 128 bits, I assume to make implementation on…
[flagged]
I agree with you, but we must admit that The Expanse has all of spaceships bouncing around, explosion sounds, and superhumans.
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..."
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.
I think this is _Alignas/alignas. struct foo { _Alignas(64) float x,y; _Alignas(64) int z; }; _Static_assert(sizeof(struct foo) == 192, "");
Decades ago they used to pull completely off the can (think Jimmy Buffet "stepped on a pop-top").
I should barely be listed as a co-author on what Claude does for me. Hiding Claude's contribution feels about as true as a combover to me.
That's kind of what reddit used to feel like when it was brand new. Can you believe it?
I have found qwen 3.8's coding quality using opencode to be similar to claude or gpt from 6-9 months ago, except much slower.
My rule of thumb is that integer ops cost 1 cycle except divides, floats 3 but maybe divide is a bit more, then integer divides are like infinity at 20+ cycles that cannot be amortized by vectorization. When you code…
They're typically like a 3-cycle op, right? Obviously that's not zero, but as far as floating point ops get it's a cheap as it gets, like an add, mul, fma, that sorta thing.
Don't forget SubEthaEdit! That was the first multiplayer editor I recall. Never found a use for this sort of thing once novelty wore off. :/
I don't think there is necessarily one ideal middle ground here. It still feels to me like what's best is a function that depends on who and when. I see it as something like a personal gradient descent. You're working…
Yeah it makes me sad too. It's a one-way veil, no going back once I experienced the new magic. Sometimes I pop back into a terminal, mkdir, git init, crack my knuckles to do some all-natural hacking and the sadness sets…
On about day 2 of using Fable I realized that the .vimrc I'd been maintaining for 15-20 years would probably never change again. With Opus I still feel like I'm pair coding and want to get in there and make some changes…
I have never seen Codex or Claude get manual memory management wrong. I used to be pretty fastidious about using leak sanitizer or other such tools to catch my own memory management issues, and while not quite useless,…
Part of that could be ABI constraints. There are some surprising calling convention differences between a vector and a struct or union with vectors in it, and they vary platform to platform. E.g. on ARM a struct with…
I hate to admit it, but the Corona "Change your Latitude" ads are what locked it in for me.
what I mean here about NaNs is that from a testing perspective, I want to be able to write a test that expects NaN in the same way that I write other expectations, and you can't do that with ==. assert(x == 7); // fine…
My preference in tests is a little different than just using IEEE 754 ==, _Bool equiv(float x, float y) { return (x <= y && y <= x) || (x != x && y != y); } which both handles NaNs sensibly (all NaNs are equivalent) and…
Yes, it's a "Brain float", basically an ordinary 32-bit float with the low 16 mantissa bits cut off. Exact same range as fp32, lower precision, and not the same as the other fp16, which has less exponent and more…
The closest term I know is "just-so story".
I am also not looking forward to the system transitioning from "big experiment, burn money to make it good" to "established business unit, tweak it to death for incrementally more money / personal promotion." We're…
If I remember correctly, the AVX2 feature set is a fairly direct upscale of SSE4.1 to 256 bit. Very few instructions even allowed interaction between the top and bottom 128 bits, I assume to make implementation on…
[flagged]
I agree with you, but we must admit that The Expanse has all of spaceships bouncing around, explosion sounds, and superhumans.
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..."
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.
I think this is _Alignas/alignas. struct foo { _Alignas(64) float x,y; _Alignas(64) int z; }; _Static_assert(sizeof(struct foo) == 192, "");