Retr0id

31 ms·

901.
by Retr0id 7mo ago
Unless I missed it the writeup never identifies a causal bug, only things that made recovery harder.
902.
by Retr0id 7mo ago
This is obviously LLM output, but perhaps LLM output that corresponds to a real scenario. It's plausible that Claude was able to autonomously recover a corrupted fs, but I would not trust its "insights" by default. I'd l
903.
by Retr0id 7mo ago
A decade or so ago, I had a clear idea of what a "native ui" should look and feel like, even if there were multiple routes to get there. I don't know any more.
904.
by Retr0id 7mo ago
https://github.com/cmc-labo/tinyos-rtos/blob/2a47496047fdb45... This codebase is essentially a stage prop, it has never been compiled nor executed.
905.
by Retr0id 7mo ago
It was pretty basic though, and even a frontier LLM might struggle to infer that OP is a negative-sentiment link, without sufficient context.
906.
by Retr0id 7mo ago
Now that we have better ML, maybe we could take "link sentiment" into account too.
907.
by Retr0id 7mo ago
You'd think, but very low quality AI-generated content regularly makes it to the HN front page, so it's just a numbers game.
908.
by Retr0id 7mo ago
so, like namespaces and cgroups?
909.
by Retr0id 7mo ago
I wish HN upvote data was public, I feel like I could build some kind of improved algorithm that reduces the vote weight of people who upvote slop.
910.
by Retr0id 7mo ago
It won't compile for anyone, it's not a real software project.
911.
by Retr0id 7mo ago
Don't forget the 71 stars on github, and counting!
912.
by Retr0id 7mo ago
Did you never even try compiling it?
913.
by Retr0id 7mo ago
It doesn't implement task switching at all...
914.
by Retr0id 7mo ago
It doesn't even compile, the whole thing is evidently built on vibes.
915.
by Retr0id 7mo ago
https://github.com/cmc-labo/tinyos-rtos/blob/2a47496047fdb45... "Context switch (to be implemented in assembly for target architecture)" There's no asm in the repo so I can only assume this is
916.
by Retr0id 7mo ago
Aside from "exponentially" being hyperbolic, which part is unsubstantiated?
917.
by Retr0id 7mo ago
Someone's LLM will comment out that line the moment it causes a build failure
918.
by Retr0id 7mo ago
Also, endian-correct code is usually semantically clearer. For example, if you're reading network-ordered bytes into an int, an unconditional endian swap (which will produce correct results on LE systems but not BE) is less clear than
919.
by Retr0id 7mo ago
I value correct code for purely selfish reasons. The most likely person to try to run my code on a BE system is me.
920.
by Retr0id 7mo ago
> There are countless rare machines that your code doesn't run on--what's so special about big endian? One difference is that when your endian-oblivious code runs on a BE system, it can be subtly wrong in a way that's ha
921.
by Retr0id 7mo ago
Until this moment I assumed .ms was a Microsoft TLD, but indeed it is not https://en.wikipedia.org/wiki/.ms
922.
by Retr0id 7mo ago
A more direct source for the screenshot: https://old.reddit.com/r/InternetIsBeautiful/comments/1qz3it...
923.
by Retr0id 7mo ago
Whitebox cryptography is widely deployed, in browser plugins for DRM.
924.
by Retr0id 7mo ago
What they describe is snake oil. Even if you assume it is mathematically possible in the general case (which is debatable!), it'll likely have a huge performance overhead. See https://en.wikipedia.org/wiki/Indist
925.
by Retr0id 7mo ago
Minification is not obfuscation and obfuscation is not security, but no amount of deobfuscation will recover the comments in the source, which are often more insightful than the source itself.
926.
by Retr0id 7mo ago
Not really, no.
927.
by Retr0id 7mo ago
If you're git bisecting a flakey test, normally your only option is to run the test many times until you're ~certain it's either flakey or not flakey. If your test suite is slow, this can take a long time. One way to think ab
928.
by Retr0id 7mo ago
Multiset hashing is not related to the domain separation problem, but it is related to the broader "signing data structures" problem. (I realise my comment reads a bit unclearly, it's basically two separate comments, split af
929.
by Retr0id 7mo ago
Putting domain separators in the IDL is interesting but you can also avoid the problem by putting the domain separators in-band (e.g. in some kind of "type" field that is always present). Tangentially, depending on what your input
930.
by Retr0id 7mo ago
Super cool! A related situation I was in recently was where I was trying to bisect a perf regression, but the benchmarks themselves were quite noisy, making it hard to tell whether I was looking at a "good" vs "bad" comm

More ›