alilleybrinker

7 ms·

31.
by alilleybrinker 2y ago
Yeah, I think you're conflating the arguments of "Weapons of Math Destruction" and "The Unaccountability Machine" here. "The Unaccountability Machine," based on Mandy's summary in the OP, argues that
32.
by alilleybrinker 2y ago
Cathy O'Neil's "Weapons of Math Destruction" (2016, Penguin Random House) is a good companion to this concept, covering the "accountability sink" from the other side of those constructing or overseeing systems.
33.
by alilleybrinker 2y ago
Steel seems alright: https://github.com/mattwparas/steel There are other Lisps too ( https://github.com/alilleybrinker/langs-in-rust ) though I think they’re less actively maintained.
34.
by alilleybrinker 2y ago
Orin Kerr's analysis of this new ruling, which is linked from the Tech Crunch article, helps break down where the specific splits with other courts lie. This is useful even if you don't agree with Kerr's analysis of the valid
35.
by alilleybrinker 3y ago
Since they actually make a product using their patented technology, they would definitionally not be a patent troll. Even if they’re litigious, that’s exactly how the system is supposed to work when you’ve invented a valuable technology whi
36.
by alilleybrinker 3y ago
I think this article is _closer_ to right than a lot of writing on programming paradigms is, but still misses a central idea. Programming paradigms can't be defined intensionally, by listing their features, nor extensionally, by listin
37.
by alilleybrinker 3y ago
Oh yeah Aria’s writing is excellent. https://faultlore.com/blah/
38.
by alilleybrinker 3y ago
Always worth plugging “Learning Rust with Entirely Too Many Linked Lists,” the canonical writing on the type of iterative approach for implementing data types with circular references in Rust: https://rust-unofficial.github.io&#x
39.
by alilleybrinker 3y ago
Bob Nystrom (munificent) addressed in elsewhere in this thread, and I’ll repeat his point here: vendoring does make a meaningful difference, because he’s taking responsibility for the code. Separately, I do hope VEX becomes more real /
40.
by alilleybrinker 3y ago
Yeah, I'd put the blame for that on the tools / systems which consume and report this kind of vulnerability data. They (at least as far as I've seen) don't really differentiate between severities of vulnerabilities. On t
41.
by alilleybrinker 3y ago
It seems like the RustSec "unmaintained" notice worked as intended. Unmaintained dependencies represent a latent security risk as they will almost certainly not respond to any future vulnerability; identifying this risk before an
42.
by alilleybrinker 3y ago
(Assuming this is the same case; I haven't been following Craig Wright closely) It looks like the case was very swiftly decided against Wright. Here's reporting from The Guardian about it today: https://www.theguardian.
43.
by alilleybrinker 3y ago
To be clear, I wasn’t staking anything as my position. I was summarizing the position of the author.
44.
by alilleybrinker 3y ago
At the moment there's an effort from the Office and the National Cyber Director (ONCD), CISA, NSF, DARPA, and OMB to encourage a move to memory safe languages, including but not limited to Rust (see [1]). This included an RFI for which
45.
by alilleybrinker 3y ago
I agree that there are details to sincerely work out here. I know in earlier drafts the wording of the "commercial" definition was such that it could be read to classify cases like a solo OSS developer who makes $10/month fro
46.
by alilleybrinker 3y ago
Yeah, the doc acknowledges this concept is "drawing on tort law principles." In this case the author, Jim Dempsey, is proposing a rules-based framework for establishing a floor regardless of what underlying system is used (warrant
47.
by alilleybrinker 3y ago
Cool thing to note: this argument was made a lot in responses to the Office of the National Cyber Directors' recent Request for Input on improving open source software security. That said, there's a state of tension on this topic
48.
by alilleybrinker 3y ago
I think this reading is _mostly_ right. To make it a little clearer: 1. A rules-based approach to define a minimum standard, likely based around existing descriptions of software weaknesses where the rules basically say "you aren'
49.
by alilleybrinker 3y ago
It’s not mentioned in the article, but I also think that learning how to debug and observe the behavior of C programs is useful given the limited ability to catch issues at compile time and high likelihood of code weaknesses and errors in C
50.
by alilleybrinker 3y ago
Just a small clarification here. The author isn’t just a fan of Rust. Steve was a member of the Rust Core Team for years and was co-author of the book “The Rust Programming Language,” which is the main recommended introductory text for the
51.
by alilleybrinker 3y ago
There’s also a bit of “have your cake and eat it too” with claiming as a benefit how stable C++ is (so old code continues working forever), while also claiming they can’t be judged against the security of old code.
52.
ISO C++ Directions Group response to RFI on open source software security(regulations.gov)
3 points by alilleybrinker 3y ago|3 comments
53.
by alilleybrinker 3y ago
I got a chance to teach Rust as part of an undergraduate introduction to programming language theory class way back in 2016-2017, and spoke about it at RustConf 2017. Here's the video for the talk: https://www.youtube.com&#x
54.
by alilleybrinker 3y ago
I feel like this isn't the first time I've read about issues with schedulers-in-schedulers, but I also can't find any immediate references on hand for other examples. Anyone know of any?
55.
by alilleybrinker 3y ago
Gleam is written in Rust and is a nice example (besides Rust itself) of what it looks like to write a language in Rust. By my own tracking ( https://github.com/alilleybrinker/langs-in-rust ) Gleam is one of the most popu
56.
by alilleybrinker 3y ago
Note that in general, the Rust project has chosen a time-based, not feature-based, release model. New Rust versions come out every 6 weeks, and new Rust editions have a consistent cadence of every 3 years. There are advantages and disadvant
57.
by alilleybrinker 3y ago
To pick out one example of what makes it challenging: not all executors place the same type system constraints on tasks they execute. Tokio, for example, is a work-stealing executor which requires tasks to implement the `Send` trait so they
58.
by alilleybrinker 3y ago
Agreed on the grandstanding! I can’t think of another topic area where the option space is extremely rich and full of trade-offs and the discussion space is so full of strong claims of there being one obvious and unquestionably best solutio
59.
by alilleybrinker 4y ago
If anyone is interested in other programming languages also written in Rust, there's a community-maintained list! https://github.com/alilleybrinker/langs-in-rust
60.
by alilleybrinker 4y ago
The RFC trying to introduce sigstore for RubyGems is an interesting look at this in practice: https://github.com/rubygems/rfcs/pull/37

More ›