HNHacker News
TopNewBestAskShowJobs

humanrebar

12,138 karma · joined February 8, 2013

submissionscomments
humanrebar··on The xz attack shell script
Autotools need to go away, but most of the underlying use cases that cause build system complexity comes down to dependency management and detection. The utter lack of best practices for those workflows is the root cause of complexity. There is no way to have a mybuild.toml build config on the face of those challenges.
humanrebar··on XZ: Repo maintainer Lasse Collin responding on LKML
Compilers and programming languages tend to be under supported (or overcomitted?) for what it's worth. They're definitely not solo projects, but certain features and components can be basically that way.

I take some of the recent concern from the Rust community about burnout and such to be early stage discovery of the economic problems in maintaining nontrivial infrastructure as a common good.

humanrebar··on Refix: Fast, Debuggable, Reproducible Builds
What about debuginfod instead? Look up your source and even your debug symbols by your build identifier.
humanrebar··on Xz: Can you spot the single character that disabled Linux landlock?
The better fix would be to move to proper dependency management and depend on a version range of a dependency instead of hoping you can do a better job of modelling the same with strings hardcoded into a CMakeLists.txt.
humanrebar··on Xz: Can you spot the single character that disabled Linux landlock?
Universal support of SARIF by compilers would be most of that.
humanrebar··on Xz: Can you spot the single character that disabled Linux landlock?
I'd prefer if the ecosystem standardized on some dependency management primitives so critical projects aren't expected to invent buggy and insecure hacks ("does this strong parse?") in order to accurately add dependencies.
humanrebar··on See, this is why I retired early from software engineering
The argument is that various steps in the backdoor relied on hacks and tech debt in autotools that are taken as arcane but normal, like detecting whether certain dependencies exist by trying to compile snippets of code. Instead of, you know, just having build systems, dependency management, and such.
humanrebar··on After Appalachian hospitals merged, their ERs became much slower
Yeah, a libertarian would let you buy penicillin from a pharmacist without a prescription, so you wouldn't need an ER visit to see a doctor to get the obvious prescription written before next week.
humanrebar··on Why isn't dental health considered primary medical care?
Routine dental care is routine, so calling it "insurance" is really odd in my opinion. Insurance isn't mainly providing protection against tail risk when it comes to eye care, dental care, and even predictable routine checkups. Obvious exceptions exist for accidents that require surgery to eyes or the inside of the mouth, but a dental hygienist (for instance) wouldn't be the healthcare professional involved in those procedures.

It could make sense for some categories of routine care to be included in insurance because they reduce risk or are cheap enough to be affordable perks of the insurance product. I just wouldn't call those features insurance.

If you're unconcerned about health insurance compared to health care as such, that's also OK. But the US healthcare system is mostly not a single payer healthcare system, at least not right now.

humanrebar··on C++ Safety, in Context
Gradual and targeted rewrites are at least an order of magnitude more affordable.
humanrebar··on C++ Safety, in Context
Yeah, that's a valid take. But if that's true, then Rust isn't giving them an edge (yet?). So it isn't the most important engineering task.

If you're saying there's no technical path to success for Mozilla... well, that might be true, but I could see that being demotivating for Mozilla engineers.

humanrebar··on C++ Safety, in Context
Well, pay attention and hold them accountable.

But Microsoft (for instance) certainly has incentives to avoid being the next Boeing or Volkswagen with respect to being excellent box checkers that end up missing the mark on the outcomes those checkboxes are supposed to protect against. It doesn't matter if C and C++ have fewer CVEs as such if Microsoft tools and platforms gain a reputation as being insecure or unsafe.

humanrebar··on C++ Safety, in Context
Mozilla also has struggles staying competitive with its core products. The main criticism of Rust as a solution to safety concerns is about that kind of outcome.

Obviously Mozilla's challenges are multifaceted and don't boil down to user-invisible code rewrites. But, at best, switching to Rust was an orthogonal engineering concern that has opportunity costs.

humanrebar··on C++ Safety, in Context
> I don't know about this. There are a lot of people being paid by their companies to work on the C++ committee and on various compiler teams.

The standards document isn't the same as a C++ implementation. The implementations are actually behind the standards, at least given current contribution levels.

There are relatively few people making significant contributions to C and C++ in compilers. Funding for middle and backend features to compilers are a lot easier to justify and fund because it looks like more straightforward optimization payoffs.

A lot of the effort put into C++ implementation work goes to keeping up with the pile of features added to the C and C++ standards every three years or so.

humanrebar··on C++ Safety, in Context
> ...the actual output of the standard's committee is so far behind

The committee just publishes documents. It is actually far ahead of C++ implementations.

The committee would probably move faster if there were more attention (and funds and volunteer work) spent on advancing C++ implementations. This especially seems true for safety and security concerns as they tend to have more tangible problems to solve than the other kinds of standards proposals.

humanrebar··on C++ Safety, in Context
Or you can flip it around and ask why there isn't a body in the C and C++ community funding tangible advancements in the security and safety problem space the way the Python Foundation and Rust Foundation are.
humanrebar··on C++ Safety, in Context
He addresses this point in the article as well, discussing risks that that language community gets too fixated on one kind of safety while attackers shift to other concerns like supply chain, code injection, or leaked credentials.
humanrebar··on How to Structure C Projects: These Best Practices Worked for Me
CMake can detect when new source files are added and rerun itself. You need to know how to spell that option when globbing though.
humanrebar··on How to Structure C Projects: These Best Practices Worked for Me
CMake supports globs. It just has notes in the reference docs about why that can lead to slower build times or even incorrect builds (like undetected new files) in some cases.
humanrebar··on How to Structure C Projects: These Best Practices Worked for Me
Now add an address sanitizer pass, reasonable unit tests, and wire it up to CI so you don't accidentally break things or trash memory.
humanrebar··on How to Structure C Projects: These Best Practices Worked for Me
But C ships to all sorts of places, so why would C limit its options by limiting its support to its own package manager?
humanrebar··on How to Structure C Projects: These Best Practices Worked for Me
If you're writing C, you might not want tools written in higher level languages required for your build environment.

This is why you still see a lot of important C project support autotools even though it's a pretty awful developer experience.

humanrebar··on How to Replace Your CPAP in Only 666 Days
I'd rather go the other way and not require a prescription for a breathing machine. They're not habit forming and you won't OD on breathing.
humanrebar··on Two handy GDB breakpoint tricks
C++26 is slated to include std::breakpoint and a couple related features. I'm expecting we'll see more portable and consistent tech for writing recoverable assertions going forward.

https://en.cppreference.com/w/cpp/utility/breakpoint

humanrebar··on C23: A Slightly Better C
The entities and their destructors still have names that the compiler and linker understand. Programs just can't name them.
humanrebar··on The Rust project has a burnout problem
I'm the opposite. There's no clear notion of status, remaining concerns, priority, etc. in an email thread.
humanrebar··on Memory safety is necessary, not sufficient
Swift is an interesting option, though that interop requires dropping support for non-clang toolchains, and I don't see that happening any time soon. I mean, it makes sense for code that exclusively targets Apple platforms, and maybe that's all that Apple and the Swift team care about?
humanrebar··on Cog: Use Python in your source files to generate pieces of code (2021)
I expect wider convergence on better build tools like CMake has made it relatively easier to perform custom build time logic like code generation without disrupting consumers of projects by changing or otherwise adding complexity to the build process.
humanrebar··on What We Watched: A Netflix engagement report
Also less objectification of women in the update.
humanrebar··on What We Watched: A Netflix engagement report
Could be worse. Other companies sell diabetes, lung cancer, and debt.
← PreviousPage 3 of 34Next →