Posts by kornel@mastodon.social
(DIR) Post #AizCUh5mOfDxYape2y by kornel@mastodon.social
2024-06-16T13:10:43Z
0 likes, 1 repeats
I've compared nearly all Rust crates.io crates to contents of their git repositories. Here's a dump of this data (33MB compressed, 150K files): https://lib.rs/data/rust-repo-checks.tar.xzThe comparison algorithm and the JSON format is described here:https://gitlab.com/lib.rs/main/-/blob/main/tarball/src/comparator.rs
(DIR) Post #Ak5lwvSFDORRNHVRbc by kornel@mastodon.social
2024-07-19T14:41:59Z
0 likes, 0 repeats
@aliss @isibell We've been looking for programmes who don't write bugs for 40 years, but we'll find them any day now. Telling them they suck and should be smart instead has to work eventually.
(DIR) Post #AlfPqtoRFZCB2mgIpk by kornel@mastodon.social
2024-09-04T10:52:08Z
0 likes, 1 repeats
Firefox will reconsider supporting JPEG XL if they get a Rust implementation:https://github.com/mozilla/standards-positions/pull/1064This is a very good news for web standards:https://mastodon.social/@kornel/113078862354601952and will fix a blocker that is hurting adoption of JPEG XL. The reference implementation has unfortunately been written in C++ just as browser vendors started looking into migrating away from C++ for security reasons, and saw the C++ codec primarily as a big new attack surface.
(DIR) Post #AltdzoVEToWGkmHWme by kornel@mastodon.social
2024-09-11T13:27:17Z
7 likes, 5 repeats
For a programming language that is definitely not a religion, this looks suspiciously like a church:#rustconf #rustlang
(DIR) Post #AlthuTa3EyqkEVFJZ2 by kornel@mastodon.social
2024-09-11T15:09:08Z
0 likes, 0 repeats
@m0xee @profdc9 To be clear, my post is meant to be a joke. I don't endorse the us-vs-them language wars.
(DIR) Post #AmPO6TSPkAWlIipqMq by kornel@mastodon.social
2024-09-26T18:25:39Z
0 likes, 0 repeats
@mattly @stonebear I've just responded to a single toot that @janl boosted where you wanted to disable 2FA in a tantrum. It's just not a sensible reaction to a reasonable requirement.There are much bigger problems, but your defiance isn't solving them, and would just create more if 2FA wasn't mandatory.
(DIR) Post #AmPO6UPcC3smGKX7dw by kornel@mastodon.social
2024-09-26T18:48:03Z
0 likes, 0 repeats
@mattly @stonebear @janl As for your post: 1. You're taking "supply chain" too literally. It's not a good term. The loosely-collaborative software phenomenon that emerged merely got a professional-sounding label slapped on it, even though it doesn't have a good real-world analogy.The fact that you don't fit a definition of a "supplier" doesn't mean you're not involved in this software-thing, only that the label given to it doesn't properly describe who the participants are.
(DIR) Post #AmPO6V1ttiVWB4RhJo by kornel@mastodon.social
2024-09-26T18:54:58Z
0 likes, 0 repeats
@mattly @stonebear @janl 2. And you've used "FOSS" term for what is OSS, but that's not surprising, since it was designed to be confused. ESR's OSS has intentionally hijacked FSF's collective ideas to shift them into a system that can easily commercially exploit unpaid labor. The fact that we have a mountain of OSS code for which nobody gets paid, and companies can resell for free is OSS working exactly as intended.
(DIR) Post #AtANjrdzHefLRHhs4O by kornel@mastodon.social
2025-04-16T01:34:48Z
4 likes, 1 repeats
What if C isn't portable, only non-C-compatible architectures went extinct?I'm half joking, but:VLIW/EPIC architectures are dead, despite CPUs desperately needing instruction-level parallelism.Instead of SIMT we have hyperthreading at home, and bug-prone threads with context switching in software.Instead of hierarchical memory, we waste 8 bytes on all pointers & emulate thread-local memory in software. Larabee was DOA & SIMD barely exists. MOS6502-style stack+registers are only on GPUs.
(DIR) Post #AtXk1o8ARw1Zj5Q0WW by kornel@mastodon.social
2025-04-27T22:43:27Z
1 likes, 0 repeats
SIGBOIVK 2025 [PDF, p170]: https://sigbovik.org/2025/proceedings.pdf`ccdoom` is a standards-compliant C23 C compiler that has "program-agnostic compilation model" and "advanced whole-program dead-code elimination" that always outputs doom.exe.> ccdoom adopts a more user-centric approach to safety: the output contains significantly more monsters than the output of most C compilers, but the user is provided sufficient ammunition to defeat them.
(DIR) Post #Ata7ksRnvvOZPJz18a by kornel@mastodon.social
2025-04-29T08:04:39Z
1 likes, 0 repeats
@soviut only ~half of TLDs tho. It rejects 773 valid TLDs.As the owner of goof@img.horse, I'm outraged.
(DIR) Post #AtcPvKwL2aBCA7K2OO by kornel@mastodon.social
2025-04-30T13:57:18Z
0 likes, 0 repeats
@foone echo > DAICON
(DIR) Post #Ay7MZboFxWjSr8Q35k by kornel@mastodon.social
2025-09-12T02:46:51Z
1 likes, 0 repeats
#EU: you can't abuse DRM to charge 30% for what costs 3% on the free marketApple: but we've bundled it with nice features!EU: price‑gouging is illegal, unbundling it is your problemApple: ok, have the 3% fee, but we add a 27% fee for using our mandatory DRMEU: noApple: ok, we'll keep the DRM, and demand different fees that will cost Fortnite 30% of their revenueEU: no#Apple: we've tried everything! it's literally impossible to understand why EU keeps fining us for non-compliance!
(DIR) Post #AyeyI9eGZBqMiH0c5Y by kornel@mastodon.social
2025-09-28T08:52:44Z
0 likes, 0 repeats
@musicmatze I prefer it over having a ton of mod.rs files.
(DIR) Post #AyeymfRwtWBU1xnUZ6 by kornel@mastodon.social
2025-09-28T08:58:20Z
0 likes, 0 repeats
@musicmatze It's possible to have peace by skipping that file entirely using inline mod instead mod foo { mod bar;}
(DIR) Post #AyjGijEbSMVoPxfM1Y by kornel@mastodon.social
2025-09-28T16:39:25Z
0 likes, 0 repeats
@harrysintonen A platform that needs to run dev tools itself (rather than being a compilation target), but isn't supported by LLVM seems to be a niche of niches.
(DIR) Post #AyjGkhic410WIMe2jo by kornel@mastodon.social
2025-09-29T13:07:44Z
1 likes, 0 repeats
@chainq There's definitely a mismatch of values, and Rust is future-looking rather than backwards-looking.Rust is 10 years past 1.0 release. The implementation is quite mature in what it targets.Lack of obscure/legacy things is immaturity only if you assume having them is a goal, but Rust prioritized other things, like safe multithreading, early WASM support, modules, error handling, metaprogramming, UB prevention/detection. From Rust's perspective these are woefully immature hacks in C.
(DIR) Post #AyjGlZIwpeZ0UP3JEO by kornel@mastodon.social
2025-09-29T18:15:50Z
0 likes, 0 repeats
@AnachronistJohn it's cool that it's possible, and I don't have anything against it. But if I'm forced to choose between writing software that might run on SuperH (but probably won't due to speed & RAM requirements) vs being able to write more reliable software that runs better on still-manufactured CPUs, I choose the latter. I also gain access to thousands of new libraries, with better interfaces, and painless support for Windows. I can do more things in practice, and find them more valuable.
(DIR) Post #B0X5HBXGBQVA5MSQBE by kornel@mastodon.social
2025-11-22T01:14:53Z
1 likes, 0 repeats
@harrysintonen In this outage the root causes spanned more than a single line, and the fixes should be deeper.However, I think in general it's still ok to question whether the language should have prevented a problem.1) Rust proclaims that certain classes of bugs in C programs are C's fault, so it's fair to ask what classes of bugs in Rust programs are equally Rust's fault.2) Rust has ambition to do better than just shrug and blame programmers for making mistakes.
(DIR) Post #B2xti0K1nOG3D9HfXs by kornel@mastodon.social
2026-02-04T02:58:05Z
1 likes, 0 repeats
@matthew @jaypatelani The unsupported ones are: Itanium, VAX, and HP PA-RISC. SH3 is partially supported (Rust with a GCC back-end can target Dreamcast)