“Andy Brinkmeyer”?
Our names are too similar and we both like Rust. We must be destined to do battle
Remote
Andrew Lilley Brinker
@alilleybrinker@hachyderm.io
mastodon 4.7.3🦀 #rustlang / 🐦 #jj / 🍄 #atproto / 📦 #opensource
⚠️ CVE / ✅ Hipcheck / 🔎 OmniBOR
🔵 Principal Engineer at MITRE (opinions are mine)
Mostly posts on BlueSky.
0 Followers
0 Following
19 Posts
Joined February 11, 2023
BlueSky Bridge:
Personal Website:
Pronouns:
he/him
keytrace:
did:plc:geozyv62fx63m7jhr4eraubc
Replying to
They don’t name themselves. It’s unclear if this is an official ISO C++ response.
Their response tries to muddy what safety means, argues a strawman about Rust having vulnerabilities too, suggests “profiles” for C++ should fix everything anyway, hints thah C++ critics are actually just talking about old C++ (in the same breath they argue that C++ is great because it’s always stable so old code sticks around forever), and that really you should give C++ more money.
#rust #rustlang
New from me in the ACM Queue: "Memory Safety for Skeptics," where I argue in favor of pursuing memory safety amid competing priorities, and how to do it!
Replying to
It is so deeply weird to me that this group would write and submit a public document defending C++ to an RFC that includes as a core priority supporting the move away from memory unsafe languages, and then wouldn't sign their names.
All but one other response to the RFC, 105 total, is a named organization, a named individual or individuals, or has no name field filled out and minimal content.
Theirs is the only semi-professional submission which is explicitly "anonymous"
#rust #rustlang
Replying to
RE: @yossarian@infosec.exchange
Seems obviously right. At the very least, this will test vendors' claims that they can quickly detect bad packages pre-installation; if that's true, then a widespread cooldown policy wouldn't cause windows of opportunity to widen.
Replying to
@mo8it@fosstodon.org Bjarne about to start ending every essay with “Rust delenda est” (https://en.m.wikipedia.org/wiki/Carthago_delenda_est)
Replying to
@mo8it@fosstodon.org haha, reminds me of a thing I wrote on Twitter back in 2019. I've reproduced it here since Twitter is a tire fire now: https://github.com/alilleybrinker/notes/blob/main/technostructuralism.md
Replying to
@corpsmoderne@mamot.fr @mo8it@fosstodon.org Some sample links of how hard it is to hold C correctly: https://pinboard.in/u:alilleybrinker/t:c/
Replying to
@miguelraz_t@hachyderm.io the Language Wars have escalated to covert ops lol
Replying to
@thephd@pony.social C++ Directions Group losing their minds
Checkout out Mastodon and once again being annoyed at the lack of quote posts, even just to quote yourself
Replying to
@cliffle@hachyderm.io @mo8it@fosstodon.org glad you liked it! 😄
Hipcheck 3.15.0 is out!
Includes prebuilt binaries for Arm64 Linux, improved affiliation analysis, better errors for bad policy files, better detection of SPDX SBOMs, and improved query registration in the Rust SDK!
We usually think of open source as being volunteer-based, but corporations are pervasively involved in open source software.
Their impact is enormous and under-recognized.
In this post I dive deep on the history, market forces, ecosystem effects, and options for action to make open source more resilient to corporate capture and expand options for support.
https://www.alilleybrinker.com/blog/open-source-software-and-corporate-influence/
@phooky@octodon.social There is an unstable feature for inferring the length. https://github.com/rust-lang/rust/issues/85077
Replying to
@laund@hachyderm.io I thought the same thing