mimd

8 ms·

1.
by mimd 2mo ago
I was never great at spelling. But at least it now has the plus of showing I'm not AI.
2.
by mimd 2mo ago
I'm not fully sure of what is the total composition of opinions, and will not dismiss your experience. Indeed the hyper privacy all high costs group might be a small percentage. But I know several that use tails openly, despite being v
3.
by mimd 2mo ago
I have met women in tech who have been privacy conscious and paranoid about state control. Or even a healthy stream of non-tech women worried that it will be used to attack their sex and to discriminate. I don't think the author is cor
4.
by mimd 4mo ago
So, no one's buying our textbooks anymore, it's getting costly to do our work, stop over claiming results for your marketing and insulting our work? I would have stuck with that. Everything else seems to be organizational or stand
5.
by mimd 4mo ago
New to the field? Intel did xeon max in the last gen, with 64GB HBM 2e, 1.6TB/s per 56 cores. It was not a great success.
6.
by mimd 4mo ago
The nice thing about the Internet is that a person, great or small, can voice their grandiose and yet myopic views of a problem and their absurd solutions to it...freely.
7.
by mimd 6mo ago
Considering that the rant is using photos from Star Trek and Oliver Twist to make their points, copyrighted material with no indication of permission, they're less "creative" than a stochastic parrot.
8.
by mimd 7mo ago
I'm annoyed at the cost statement, as that's the sleight of hand. "$20000" at current pricing. Add some orders of magnitude to the costs and you'll get your true price you'll have to pay when the VC money start
9.
by mimd 8mo ago
Opensource is a bit more complex than being a "public good". They're focusing on the low cost as a jump starting point, which make me doubt their sincerity/understanding about managing that relationship healthily.
10.
by mimd 8mo ago
It's not going to solve the housing issue and is mostly for press (and it's not even getting into ulterior motives), but it might help with preventing a longer term issue of large investors becoming a major issue. Additionally, I
11.
by mimd 9mo ago
Huzzah! You made it to the big leagues Rust! Come join C over here with the "CookiesVE".
12.
by mimd 1y ago
I suggest waiting till the gcc side matures, with the minimum of a working gcc frontend for a non optional dependency. Optional dependencies with gcc_codegen might be okay. Git is pretty core to a lot of projects, and this change is risky,
13.
by mimd 1y ago
Rudimentary analysis of five battles spread out over a 1500 year period; supposedly supporting sources that upon examination state their unsureness; stating propaganda casualty numbers without a hint of irony to justify; allows you to unequ
14.
by mimd 2y ago
No, it can track pointer bounds and validity across functions. It also targets identifying cases of UB via eva. Both rust and frama-C rely on assertions to low level memory functions. Rust has the same gaping UB hole in unsafe that can cros
15.
by mimd 2y ago
Yes, I know the policy that has been stated and the recent docs on it ( https://rust-for-linux.com/rust-kernel-policy ). A good portion of the R4L group were trying to avoid this scenario due the toxicity of such a change (es
16.
by mimd 2y ago
"But for new code / drivers..." encompasses more than just "drivers" and refers to all new code. I doubt it's a mistake either due to the way the rest of the email is written. And Greg said "no one sane ev
17.
by mimd 2y ago
https://llvm.org/devmtg/2023-05/slides/TechnicalTalks-May11/... Supposedly ~5% (1-29%), but I'm testing my own projects to verify (my guess is higher at 10-20%, but will depend on the code). Suppose
18.
by mimd 2y ago
Yes, panicking in kernels is bad. I've followed the whole R4L fight about working around it. https://github.com/apple-oss-distributions/xnu/blob/main/doc... https://github.com/apple-
19.
by mimd 2y ago
Isn't this a bait and switch, that all the c kernel devs were complaining about? That it wouldn't be just drivers but also all new kernel code? The lack of candor over the goal of R4L and downplaying of other potential solutions s
20.
by mimd 2y ago
If you look at the CVE lists, about 70-80% of all c memory bugs are related to OOB Read and Write. Additionally, like rust, fbounds-safety can remove redundant checks if it can determine the bounds. My question is how likely can it be adopt
21.
by mimd 2y ago
Well, it will be really funny when the executive branch starts firing all the judiciaries security (USMS JSD, under DoJ) to save costs. But secondary outcomes have either not dawned or dissuaded the recent courts on their path to increasing
22.
by mimd 2y ago
Of course they are. Any rational person not blinded by partisanship would be infuriated by this development and immediately demand that DOGE be restrained. Even most partisans would blanch and demand accountability. DOGE advocates know this
23.
by mimd 2y ago
https://www.npr.org/2025/02/14/nx-s1-5298190/nuclear-agency-... If even half of NPR's report is true, the way in which it was conducted was grossly cruel and with complete ignorance. DOGE and it&#x2
24.
by mimd 2y ago
Since the rest of the advisory is demanding full scale rewrites into a new language based on llvm that has officially nuetered it's gcc port, I don't think they really care about those sorts of concerns. Hence my annoyance at thei
25.
by mimd 2y ago
Not to fully encapture C's variadic printf, but on the macro front, I've been having fun creating type checking for macros by a constexpr allocation from a _generic switch type check of the args and then checking the result with s
26.
by mimd 2y ago
I wish they would have gone more indepth about the current compiler work, such as stack defenses or fbounds-safety. It should cover OOB read and write safety, which is 70-80% of C's memory vulnerabilities, for a marginal performance ov
27.
by mimd 2y ago
I know this article is more a buisness case presentation than a full demonstration of the field but the TR also misses some points. Why remove the refrences in the TR to frama-C, cbmc, etc. from the opinion report? They are easier to adopt
28.
by mimd 2y ago
Thanks for the input and links. I'll need to test out the costs of the mitigations. BTW, I found one of the rust rfc documents helpful for understanding the borrow checker. Do you know if there is a similar rust RFC document for the up
29.
by mimd 2y ago
If it requires the programmer to bear the responsibility for proper usage (eg. must use checked_add not rely on panic), how's that different than the issues with undefined behavior? I'm also concerned with the differing functional
30.
by mimd 2y ago
I'm confused over lines such as "Profiles have to reject pointer arithmetic, because there’s no static analysis protection against indexing past the end of the allocation." Can't frama-c/etc do that? Additionally, s

More ›