Kang Seonghoon aka lifthrasiir and many other nicknames. (Twitter @senokay, Bluesky @mearie.org, Github @lifthrasiir, https://mearie.org/) Views my own, I'm not a laywer (nor any other occupation that might require professional qualifications), your mileage may vary, yadda yadda yadda.
Brief bio: Born in South Korea. Was a wannabe programming language researcher until I realized I'm not fit for the academia. Went to several startups with various duties. Then became a gamedev---primarily server frameworks and infrastructure but did many others too---in a big company for nearly a decade until I finally burnt out. Then worked for an ML accelerator startup doing tons of systems programming. Still doing strange things over the course: one winning IOCCC entry, a full-fledged type checker for Lua, several influential Rust libraries including Chrono, compression stuffs like Roadroller and J40 etc. Known for needlessly big walls of text.
[ my public key: https://keybase.io/lifthrasiir; my proof: https://keybase.io/lifthrasiir/sigs/dGcjGsucdiIiTpeVc7WH5YfQNZnkypj-azYwkMJH60Y ]
Personally I don't think that matters, because the article is problematic enough when it can be read like ad hominem. Assuming that the question was phrased reasonably neutrally (but not necessarily free of hidden biases), the fact that LLM concluded so is an enough evidence here. Also as a non-LLM data point, I felt roughly same (especially the "softening" bit).
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.
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.
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 problems far beyond the horizon, which is often unreachable throughout the project's history. Zig can be a similar case.
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 don't normally feel so because higher educations seem "typical" to us.
> 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 have a private project (>300K LoC) that has been translated from Python to TypeScript and the reason we couldn't use Rust was definitely the iteration time.
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.
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. The overall tone is "we built the right primitive (read/edit/bash), bet on future model improvements, and it paid off."
Honestly I don't want to endure an awkward terminal interface and/or questionable design to just arrive at this conclusion.
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 are to be expected.
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.
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 modern Rust. Your point might be true for some other languages but there is a good reason to refute that for Rust.
Ah, and many F77 libraries are still in active use. Nowadays they are used via C or Python wrapper, and I guess you said "using it as it is" to disregard that, but we were talking about what original maintainers are expected to do and the original F77 authors have nothing to do in order to stay relevant here.
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.
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 across different Pandoc versions.
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 in Rust, and yes, some operations are indeed faster than others, but it was tough to compare against Rug which uses MPFR under the hood. I did fully design the library API beforehand and explicitly directed the documentation, testing and benchmark tasks, but of course all the brilliance of the library comes from Fabrice Bellard and not me.
Brief bio: Born in South Korea. Was a wannabe programming language researcher until I realized I'm not fit for the academia. Went to several startups with various duties. Then became a gamedev---primarily server frameworks and infrastructure but did many others too---in a big company for nearly a decade until I finally burnt out. Then worked for an ML accelerator startup doing tons of systems programming. Still doing strange things over the course: one winning IOCCC entry, a full-fledged type checker for Lua, several influential Rust libraries including Chrono, compression stuffs like Roadroller and J40 etc. Known for needlessly big walls of text.
[ my public key: https://keybase.io/lifthrasiir; my proof: https://keybase.io/lifthrasiir/sigs/dGcjGsucdiIiTpeVc7WH5YfQNZnkypj-azYwkMJH60Y ]