Macros are simply a fact of life in any decent-sized C codebase. The Linux kernel has some good guidance to try to keep it from getting out of hand but it is just something you have to learn to deal with.
There's a big gap of knowledge between infosec researchers and ML security researchers. Anthropic has a bunch of column B but not enough column A.
This was discussed in some detail in the recently published Attacker Moves Second paper*. ML researchers like using Attack Success Rate (ASR) as a metric for model resistance to attack, while for infosec, any successful attack (ASR > 0) is considered significant. ML researchers generally use a static set of tests, while infosec researchers assume an adaptive, resourceful attacker.
ML researchers are not sec researchers. they need to stick to their own game.
companies need to use both camps for a good holistic view of the problem. ML is the blue team. sec researchers the red.
While I didn't disagree with his general politics, he is absolutely right that the US has largely pulled up the ladder behind them. The average age of a first time home buyer is now 40.
The American dream of having a home and a family is now out of reach for millions of Americans and politicians on both sides of the aisle.
> he is absolutely right that the US has largely pulled up the ladder behind them.
You blame "the US" and you agree with Thiel who blames "capitalism"? It starts to look like a broad-brush blame game... let's add the generational trolling to it too.
As if this whole show wasn't designed by Thiel and the rest of the lobby club.
Smart kids can be a distraction as well. It certainly would have benefitted me to enter G&T at Kindergarten instead of 3rd grade. Much of my first grade was spent separate from the other kids doing 5th grade workbooks.
While I think this is Rust's biggest flaw, this doesn't stem from any particular hatred of C/C++. This is related to memory safety, as it is very difficult to reason about memory lifetimes of object graphs with cycles.
I've started to use agents on some very low-level code, and have middling results. For pure algorithmic stuff, it works great. But I asked it to write me some arm64 assembly and it failed miserably. It couldn't keep track of which registers were which.
I was there for three years and you're totally right that everything's been automated, but also there are a large number of product level decisions that just don't make sense. They make financial sense, sure, but then that means the engineer has drank the MBA cool aid (or not enough of it), things get killed off, and they are no longer to be trusted around things that need proper love and care put into them. Promo packets though, sure.
It's hard to read that as a human, though, and not want to build a system that lets people update bad map data? Which there used to be, but then yeah.
So yeah, the inmmates (engineers) used to run the asylum (Google), but then a group of fucking psychopaths (DoubleClick) got added to the asylum, got given meth (ad money) and shits fucking unhinged.
Unfortunately, c-ares is not problem-free on all platforms.
On iOS, its use triggers a local network access popup (it tries to reach your DNS server, which is often on your LAN). If a user denies acess, your app will simply not work.
On Android, it's not compatible with some VPN apps. Those apps are to blame, but your users are going to blame you not them.
So, at my previous company we ended up building libcurl with a threaded DNS resolver on both iOS and Android.
Macros are simply a fact of life in any decent-sized C codebase. The Linux kernel has some good guidance to try to keep it from getting out of hand but it is just something you have to learn to deal with.
reply