Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mtklein
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
mtklein
14d ago
Decades ago they used to pull completely off the can (think Jimmy Buffet "stepped on a pop-top").
2.
▲
by
mtklein
17d ago
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.
3.
▲
by
mtklein
19d ago
That's kind of what reddit used to feel like when it was brand new. Can you believe it?
4.
▲
by
mtklein
28d ago
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.
5.
▲
by
mtklein
1mo ago
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 simd it's best to
6.
▲
by
mtklein
1mo ago
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.
7.
▲
by
mtklein
1mo ago
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. :/
8.
▲
by
mtklein
2mo ago
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 on a
9.
▲
by
mtklein
2mo ago
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 in before the
10.
▲
by
mtklein
2mo ago
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 myself, bu
11.
▲
by
mtklein
3mo ago
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, that sort of testing
12.
▲
by
mtklein
4mo ago
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 two 128-bit vectors w
13.
▲
by
mtklein
4mo ago
I hate to admit it, but the Corona "Change your Latitude" ads are what locked it in for me.
14.
▲
by
mtklein
5mo ago
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); // fi
15.
▲
by
mtklein
5mo ago
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 sens
16.
▲
by
mtklein
5mo ago
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 mantissa.
17.
▲
by
mtklein
5mo ago
The closest term I know is "just-so story".
18.
▲
by
mtklein
6mo ago
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&#x
19.
▲
by
mtklein
7mo ago
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 existing 128 bit vector u
20.
▲
by
mtklein
8mo ago
I agree with you, but we must admit that The Expanse has all of spaceships bouncing around, explosion sounds, and superhumans.
21.
▲
by
mtklein
10mo ago
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..."
22.
▲
by
mtklein
10mo ago
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.
23.
▲
by
mtklein
10mo ago
Zig is so good at this, it is also probably the easiest way to cross-compile C.
24.
▲
by
mtklein
11mo ago
I think this is _Alignas/alignas. struct foo { _Alignas(64) float x,y; _Alignas(64) int z; }; _Static_assert(sizeof(struct foo) == 192, "");
25.
▲
by
mtklein
1y ago
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 int
26.
▲
by
mtklein
1y ago
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
27.
▲
by
mtklein
1y ago
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.
28.
▲
by
mtklein
1y ago
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
29.
▲
by
mtklein
1y ago
I found this especially nice working with large SIMD constants.
30.
▲
by
mtklein
1y ago
Okay, I'll bite: 2 and 5 are prime, this is the perfect fifth problem, only approximate solutions are possible. Make me wrong!
More ›