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.
458 karma · joined January 15, 2012
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.
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?
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.
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.
"Was silence not an option?"
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.
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.
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.
https://git-scm.com/docs/git-maintenance#Documentation/git-m...
https://github.com/atuinsh/atuin/blob/5f279584f4f6532871a74d...
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.
Never thought I'd feel nostalgic about that era...
That to me seems to match the definition of survivorship bias quite well?