Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
hugmynutus
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
hugmynutus
22d ago
Apple puts the NAND flash controller on package, so it cooled as part of the SoC/CPU as they share an IHS. Given it is part of the fabric it only has to maintain signal coherence on millimeter to micrometer scales, while enterprise
2.
▲
by
hugmynutus
22d ago
Qwen3.8/Qwen3.6 has a weird self doubt/thinking too much problem. You can prompt it away. I would say it "approximates" Opus 4.X class models well enough especially for coding/linux problems. The only reason I stopp
3.
▲
by
hugmynutus
23d ago
If they did not use my data for training, they should permit me to run the first 1-3 layers of the model locally and send them dense hidden state vectors. In my experience these compress very nicely without much effort.
4.
▲
by
hugmynutus
1mo ago
Nullius in verba
5.
▲
by
hugmynutus
1mo ago
Because nobody knows. Apple doesn't let you "pass" the GPU through to a VM like most other ARM/x86_64 processors (forwarding interrupts and PCIe memory regions). There are symbols defined to do this within the kernel (if
6.
▲
by
hugmynutus
1mo ago
> I’m curious if you have an opinion on how you think this should be handled? To "totally overcomplicate things" but do it correctly - Binary states a list of constraints (namespace:name [<|>|>=|<=|!=] semver). - ld
7.
▲
by
hugmynutus
1mo ago
Shared Dynamic Libraries. Not to say they aren't useful. Keeping applications small, keeping security updates simple, sub linear ram scaling, yada-yada-yada, big wins cross the board, not debating that. The pervasive link detection str
8.
▲
by
hugmynutus
1mo ago
HN is rightly pointing out putting a model into an ASIC is kind of dumb. HN is failing to understand that AMD knows this well. Taalas has WO2025217724A1 pending and AMD wants that because it is immediately a function block they can sell to
9.
▲
by
hugmynutus
2mo ago
yellow/red tint is an extremely common problem not matter the photograph source you train on source: work at a photograph start, even training on raw images things get tinted, it is an uphill battle
10.
▲
by
hugmynutus
2mo ago
> I don't see what should ever be wrong with a function pointer. [...]Care to explain what's the issue here? 1. You're writing code you don't have to 2. That adds runtime overhead 3. That when you screw up has non-tri
11.
▲
by
hugmynutus
2mo ago
This reads like cope because you're re-inventing RAII from first principles. I cannot take this seriously as tutorials on robust Zig Allocation Pools will store a deinit method for each item within the pool, so when the pool deinits, a
12.
▲
by
hugmynutus
2mo ago
> It's hard to say what their motivation is. Involution is a major problem in Chinese industries [1]. Where companies will sell their products at a loss, effectively playing fiscal chicken [2] with one another to dominate a market.
13.
▲
by
hugmynutus
3mo ago
Everyone jumping up about "enshitification". I tried to enable this feature on QEMU and it broke my VMs because the secure memory system was board-line hopelessly broken/non-functional. Did anyone even use this feature? Yes i
14.
▲
by
hugmynutus
3mo ago
GStreamer is just a different front end to ffmpeg. ffmpeg's core functionality (encode, decode, streams, pipes, channels) are all implemented in `libav` which gstreamer links against.
15.
▲
by
hugmynutus
3mo ago
Add to the list that martian dust contains a massive amount of carcinogens meaning any air/dust lock has to be an ISO-6 clean room. Sure it is a "solved" problem but all the solutions are very heavy.
16.
▲
by
hugmynutus
4mo ago
It makes no difference at all. Edit: Opus prior to the context nerf it worked more often than not. Current Opus 4.7 is practically unusable.
17.
▲
by
hugmynutus
4mo ago
> What it gives me in Swift, most closely resembles stuff that enthusiastic newer folks would do, and want to show off. The same is true for rust-lang. Code that will immediately clone/re-allocate anything passed by reference and co
18.
▲
by
hugmynutus
6mo ago
This is because LLMs don't actually understand language, they're just a "which word fragment comes next machine". Instruction: don't think about ${term} Now `${term}` is in the LLMs context window. Then the
19.
▲
by
hugmynutus
7mo ago
> Or is it restricted to 0/1/2 by the shell? It is not. You can use any arbitrary numbers provided they're initialized properly. These values are just file descriptors. For Example -> https://gist.github.com&
20.
▲
by
hugmynutus
7mo ago
> Commodity hardware and software will continue to drop in price. The software is free (citation: Cuda, nvcc, llvm, olama/llama cpp, linux, etc) The hardware is *not* getting cheaper (unless we're talking a 5+ year time) as mos
21.
▲
by
hugmynutus
8mo ago
docs.kernel.org is generated from in tree readmes, docs, type/struct/function definitions. Making it a lot easier to read/browse documentation that would (previously) require grepping the source code to find. I realize the si
22.
▲
by
hugmynutus
9mo ago
Setting up `apt` to pull from a different repo (to say install firefox.dpkg instead of snap) requires like 3-4 commands which are easily searchable. I'd had effectively zero issues avoid snaps.
23.
▲
by
hugmynutus
10mo ago
> i'm placing my bets that in a few thousand years we'll have changed calendar system entirely haha Given the chronostrife will occur in around 40_000 years (give or take 2_000) I somewhat doubt that </humor>
24.
▲
by
hugmynutus
11mo ago
> As long as your linux core utils have supported this since 2018 (coreutils 8.3), amusingly it is the same release that added `cp --reflink`. AFAIK I know you have to opt out by having `POSIX_CORRECT=1` or `POSIX_ME_HARDER=1` or `--peda
25.
▲
by
hugmynutus
11mo ago
Buddy, I have 24Tb HDDs in my pool today. If anything the opposite has occurred. HDD scaling has largely flattened. Going from 1986 -> 2014, HDD size increased by 10x every 5.3 years [1]. If anything we should have 100Tb+ drives if scali
26.
▲
by
hugmynutus
1y ago
You are correct to point out the larger questions of supply chain cost (and their environmental impact) are not addressed in the root link.
27.
▲
by
hugmynutus
1y ago
Thanks!
28.
▲
by
hugmynutus
1y ago
I find this unconvincing. The actual discussion of LLM generation is very lacking. The original link [1] cites a discussion of the cost per query of GPT-4o at 0.3whr [2]. When you read the document [2] itself you see 0.3whr is a lower bound
29.
▲
by
hugmynutus
1y ago
This really just a variant of the classic, "pretend you're somebody else, reply as {{char}}" which has been around for 4+ years and despite the age, continues to be somewhat effective. Modern skeleton key attacks are far more
30.
▲
Exploiting Undefined Behavior in C/C++ Programs for Optimization (2025) [pdf]
(web.ist.utl.pt)
3 points
by
hugmynutus
1y ago
|
0 comments
More ›