HNHacker News
TopNewBestAskShowJobs

mtndew4brkfst

458 karma · joined January 15, 2012

Elixir, Rust, Kubernetes
submissionscomments
mtndew4brkfst··on My thoughts on the Bun Rust rewrite
I'm as anti-AI as they come and I mostly think everyone involved in this is making their respective projects and ecosystems look worse for it here.

Andrew was still way out of line in making many of the points included in this post, you don't have to be pro-AI to feel that way.

mtndew4brkfst··on My thoughts on the Bun Rust rewrite
"If this was a tweet people would be fine with it"

Actually, some folks do care about how the leader and public face of a project conduct themselves regardless of venue. If a different public figure ie some CEO wrote something reprehensible about some particular ethnic group, is it more excusable or forgivable if they did it on their personal social media account rather than the company blog? Same basic thing.

Public writing in a personal space is still public writing. Being held accountable for publicly stated views is an inherent part of sharing them in public, no?

mtndew4brkfst··on My thoughts on the Bun Rust rewrite
Other people (not meaning this about you) very frequently seem to throw around the BFDL acronym uncritically without remembering or caring that Benevolent is the first word in there.

This blog post is mostly made up of pettiness and is not an isolated incident - he is often pretty "spicy" or downright hostile in comments sections when making an appearance.

mtndew4brkfst··on My thoughts on the Bun Rust rewrite
Yes but through iterative ratcheting, some portion of that unsafe can likely be migrated to idiomatic code without unsafe. And the other 96% of the code now has more mechanical guarantees than it did before.

Static linting in Rust via clippy also makes it pretty straightforward to begin enforcing things like "unsafe blocks need to have safety doc comments" as a CI warning or failure, and there are community tools that focus on this topic too.

I can't stand the practice of "LLM porting" personally but if you're going to do a mechanical rewrite from something else into Rust, this (permit unsafe and unidiomatic but 1:1 translation at first) is a fairly reasonable strategy imo.

mtndew4brkfst··on My thoughts on the Bun Rust rewrite
Andrew's online social behavior is largely a streak of pettiness imo. This is not even close to the first time I've seen him write something I felt was overtly mean spirited, not just euphemistically "blunt".

"Was silence not an option?"

mtndew4brkfst··on Crypto in 2026: Oh, This Is the Bad Place
A lot of what else Stephen Diehl has published lately is more overtly slop, so it's a pretty safe bet.
mtndew4brkfst··on Iroh 1.0
The paid component in question here is not necessary to use Iroh, though. You can have elaborate Iroh-based projects entirely based on the OSS components without losing features and without paying anything. There are public relays and self-hosted relays, anything else is the concern of your application(s).

As for anything being a "goal"? They do have dev salaries to pay and they offer managed control planes with SLAs or consultations with the core devs to accomplish that.

mtndew4brkfst··on Iroh 1.0
Not affiliated, just a happy dev.

Nothing about Iroh usage as operator or end-user entails billable metering of keys, clients, QUIC endpoints, bytes transferred etc and to be honest you could deploy pretty extensive Iroh-based software without ever having a financial relationship with number0.

mtndew4brkfst··on Iroh 1.0
Iroh is free-to-use, permissively licensed, relays are self-hostable, and it's all fully open source for all necessary components. The only proprietary thing n0 visibly has is a managed platform for private relays with SLAs and observability. Which is IMO a bog-standard business model, it's not open-core nonsense. T There's no billable metering of users, bytes, QUIC endpoints, etc.
mtndew4brkfst··on Iroh 1.0
Relays can't observe the contents of traffic per the design, but if censorship was possible and meaningful based on the tuples of the paired connection endpoints, I guess? The public number0 relays are (honor-system) running the open source relay code that can be inspected for such behavior.

With the relay daemon being self-hostable and OSS any use-case that needs to be more censorship-resistant than that has the option to run their own relays as needed.

mtndew4brkfst··on Iroh 1.0
Presumably this has significant literal costs (because Cisco) and maybe a hardware or virtual-appliance requirement?
mtndew4brkfst··on Iroh 1.0
That is a pluggable/possible, but non-default, configuration.
mtndew4brkfst··on We're Not Building AI Features for the Money
I'm a heavily skeptical reader on the topic but I didn't really see anything more than "here's a couple ways that we find the tech useful". It didn't feel like much of an actual refutation of the commentary that the post was ostensibly written in response to.
mtndew4brkfst··on Claude Code Opus 4.7 keeps checking on malware
"The gangsters do it and get away with it so any random person should get to as well"? Not a particularly defensible position if that's an accurate paraphrase.
mtndew4brkfst··on Claude Code Opus 4.7 keeps checking on malware
What is the specific concrete purpose of downloading millions of URLs per hour across different domains if it's "not doing anything wrong"?
mtndew4brkfst··on Xilem – An experimental Rust native UI framework
If Slint's licensing terms don't bother you, that's cool. They are more restrictive than most of the Rust ecosystem being dual Apache/MIT, though.
mtndew4brkfst··on Xilem – An experimental Rust native UI framework
Was there some new developments with this project that renewed interest recently? I started learning Rust in 2018 or 2019 and I think "good Rust GUI" research is probably at least that old.
mtndew4brkfst··on Age verification on Systemd and Flatpak
Why would it be more spooky if Apple in particular did this vs all the other hardware vendors that ship a pre-installed OS?
mtndew4brkfst··on How to periodically sync a Git repository with its remote
Doesn't serve the same purpose as OP, but for the opposite direction, `git maintenance register` is a built in if all you need is periodic fetching and GC:

https://git-scm.com/docs/git-maintenance#Documentation/git-m...

mtndew4brkfst··on Atuin v18.13 – better search, a PTY proxy, and AI for your shell
It's feeding it to a remote endpoint:

https://github.com/atuinsh/atuin/blob/5f279584f4f6532871a74d...

mtndew4brkfst··on Copilot edited an ad into my PR
Small nit, but PR description bodies might wind up as part of a commit message verbatim, depending on repo settings and the merger's personal behavior. It's an easy outcome, the merger doesn't need to copy and paste or anything, and I think it might be a default or popular setting for squash-merges.
mtndew4brkfst··on Claude Code runs Git reset –hard origin/main against project repo every 10 mins
It has once even force pushed to github, which doesn't allow branch protection for private personal projects.

This is only restricted for *fully free* accounts, but this feature only requires a minimum of a paid Pro account. That starts around $4 USD/month, which sounds worth it to prevent lost work from a runaway tool.

mtndew4brkfst··on A Message from the Ruby Central Board
Colorful is an odd way to spell "vocally bigoted".
mtndew4brkfst··on Is anybody else bored of talking about AI?
The amount of questions I fielded about web3, coins, ledgers, etc as an IC speaking with customers or internal leadership was around an order of magnitude lower, and well-known brands weren't trying to sell me any of them. It was much rarer for it to get shoved into a product it wasn't helpful for, too.

Never thought I'd feel nostalgic about that era...

mtndew4brkfst··on Is anybody else bored of talking about AI?
Not limited to here, of course. Net-new publications to ArXiv for some (most?) CS subcategories are >=90% about models, transformers, training, quantization, or some other directly related field, or how to apply these towards a different specialty.
mtndew4brkfst··on The future of version control
A demo as "the future of" something doesn't really resonate with me. It's like saying a melodic motif and a couple well-written lines of lyrics are "the future of" my new music career.
mtndew4brkfst··on The future of version control
If you haven't heard of it yet, Mergiraf uses tree-sitter grammars to resolve merges using syntax-aware logic and has a pretty good success rate for my work.
mtndew4brkfst··on Diverse perspectives on AI from Rust contributors and maintainers
Not speaking for others, but Niko's writing is IMO strongly shading the wording used to describe positions that do or don't align with his own views.
mtndew4brkfst··on No AI in Node.js Core
Because people who enjoyed working with Elixir otherwise but don't want to participate or support that kind of environment have mostly left when the trend became clear. So the folks who are sticking around are the ones who are neutral-to-positive on AI. This means explicitly or implicitly surveying that group for opinions on AI's place in development work, such as while designing a conference schedule, are going to be missing most of those voices who might once have objected. It will continue to skew harder towards favoring AI in the future with most of the possible sources of more-critical opinions leaving.

That to me seems to match the definition of survivorship bias quite well?

mtndew4brkfst··on Dial9: A Flight Recorder for Tokio
Seems to be pretty substantially AI-assisted during its development.
Page 1 of 8Next →