lifthrasiir

4 ms·

31.
by lifthrasiir 3mo ago
Reality check. The confirmation that the author is not alone in having this particular feeling by using an LLM as a proxy.
32.
by lifthrasiir 3mo ago
While I understand ZSF's bittersweet relationship with Oven and agree to several points (especially preparedness), this writing is badly structured and that shows something. Hope to see him turning around.
33.
by lifthrasiir 3mo ago
The project in question needed lots of near-instant human judgements and the iteration loop had to be extremely tight. Maybe Rust should be reconsidered once it gets stabilized enough, but not right now.
34.
by lifthrasiir 3mo ago
Oh, yeah that might be confusing. I meant "you can say the same thing for GC language if that's true, which isn't necessarily true, so that must be false". More precisely speaking: GC languages are said to delay memory p
35.
by lifthrasiir 3mo ago
Claude Code is entirely vibe-coded for a long time. Bun isn't. You go read and compare the actual Bun code; it reads reasonably well [1]. [1] For example, as a random sample, https://github.com/oven-sh/bun/b
36.
by lifthrasiir 3mo ago
Hey, a typical person should be intelligent because we human have used ourselves as a de-facto definition of intelligence anyway. That sentence probably means something like "no intellectually disabled person here". Even though we
37.
by lifthrasiir 3mo ago
> There's less and less reason to use GC'd languages in the agentic coding era. Faster iteration, maybe? Rust's safety guarantee isn't exactly free (while still being very excellent) and does affect iteration time. I
38.
by lifthrasiir 3mo ago
The article explicitly mentions the maintainability as a foremost concern.
39.
by lifthrasiir 3mo ago
The same concern applies to every GC language, so it's not necessarily bad for Zig. Bun can have been grown too large for Zig to be effective, while moderately sized projects may still greatly benefit from Zig.
40.
by lifthrasiir 3mo ago
Claude itself (Opus) gave me the following conclusion: > The article frames Claude Code as the latest step in a lineage from punch cards → ed → modern editors → AI agents. Multiple team members say they no longer write any code by hand.
41.
My 11-year-old font bug(hackers.pub)
4 points by lifthrasiir 3mo ago|0 comments
42.
by lifthrasiir 3mo ago
Beeg is just a respelled version of "big" ("ee" for /i:/). Apparently it is also a name of a certain questionable website (I didn't know!), but it is a common enough word that such unfortunate conflicts ar
43.
by lifthrasiir 3mo ago
The second fact, pi^2 ~= g, is famous enough that it has a separate section in Wikipedia [1]. [1] https://en.wikipedia.org/wiki/Mathematical_coincidence#Gravi...
44.
by lifthrasiir 3mo ago
Clever students can do anything without steering anyway ;-) Typical, I mean median, students would rather struggle to learn C.
45.
by lifthrasiir 3mo ago
A universal document converter is expected to expand via adding support for additional formats---that's okay (same for your other examples). I'm much more worried about the widening scope of the project.
46.
by lifthrasiir 3mo ago
Rust compiler is famously backward compatible all the way to 1.0 (after almost a decade of zero guarantees). My codes targeting early 1.x releases still work in the modern Rust, though the convention may significantly differ from the mode
47.
by lifthrasiir 3mo ago
Creating a part of C compiler, most frequently a working optimization pass, is a regular assignment. The entirety of C compiler is too large to give it as a student assignment.
48.
by lifthrasiir 3mo ago
Is there anyone feeling that Pandoc is ever increasingly bloated? I have used Lua filters a decade ago [1] and the current documentation is nothing like my memories. I'm not even sure that how much of Lua scripts remain compatible acro
49.
by lifthrasiir 3mo ago
Just in case, this is my library and I didn't post this to the HN, because I didn't think this is that HN-worthy. Ask me anything anyway. My main motivation to port libbf was to see if it is faster than usual libraries available i
50.
by lifthrasiir 3mo ago
It wasn't one-shotted by the way, but if you have a provably correct and comprehensive library there are not many things to maintain anyway.
51.
by lifthrasiir 3mo ago
I always drooled over Sollya's fpminimax which implements a correct Remez algorithm over a floating-point domain. It turns out that fpminimax is not that special; it faithfully follows the usual approach to convert a concrete-domain pr
52.
by lifthrasiir 3mo ago
> Your final submission must be a 500 to 10,000-word short story, generated entirely by AI. No human-written prose and no post-generation editing. To verify this, you will submit your full prompt harness / setup alongside your story
53.
by lifthrasiir 3mo ago
#1 is rather what unexperienced game developers think what is a gamer's dream. It isn't---in fact, unlimited freedom is a recipe for confusion.
54.
by lifthrasiir 3mo ago
Oh, sure, the "In Popular Culture" section is a prerequisite for every Wikipedia article. ;-) In seriousness though, the Malbolge article (2003) significantly predates the TV series in question (2012--2019). I wouldn't be sur
55.
by lifthrasiir 3mo ago
As an actual esolang enthusiast (and a past Wikipedia administrator two decades ago), I can say that Malbolge is only notable because it remained unsolved for the extended period only due to the lack of serious attempts. It doesn't eve
56.
by lifthrasiir 4mo ago
See https://github.com/jimparis/qr-font/blob/master/design.md for the actual design. As who have written a QR code encoder library... I'm in shock and awe.
57.
by lifthrasiir 4mo ago
It is an explicit way to discard return values; `self.poll_read(cx)?` etc. alone would warn. Or in this case, `Poll<Result<(), Error>>` is unwrapped once and `Result<(), Error>` is being discarded. The decision to discar
58.
by lifthrasiir 4mo ago
For decompression, nothing changes because DEFLATE is asymmetric; compressor can spend however much time to optimize the compressed stream independently from decompressor.
59.
by lifthrasiir 4mo ago
Oh wow, seriously, I always thought Lua should have been like this. The 5.1/5.2/5.3+ split was so painful. > My ultimate goal was to support LuaJIT in Rust as well but this does not make it easier. I think you could stop right
60.
by lifthrasiir 4mo ago
Given its limited output dimension it's hard to tell. I haven't exactly tested fine-tuned variants but I think they would work well under certain situations. After all, some (possibly cherry-picked) examples still exhibit similar

More ›