mort96

19 ms·

481.
by mort96 6mo ago
Nothing, and there has been a push for more standardization including adopting UEFI in the ARM server space. It's just not popular in the embedded space. You'd have to ask Qualcomm or Rockchip about why.
482.
by mort96 6mo ago
> You can't have a custom kernel if you can't rebuild the device tree. What is this supposed to mean? There is no device tree to rebuild on x86 platforms yet you can have a custom kernel on x86 platforms. You sometimes need to
483.
by mort96 6mo ago
Microsoft's standardization got AMD and Intel to write upstream Linux GPU drivers? Microsoft got Intel to maintain upstream xHCI Linux drivers? Microsoft got people to maintain upstream Linux drivers for touchpads, display controllers,
484.
by mort96 6mo ago
It's not just about booting though. We solve this with hardware-specific devicetrees, which is less nice in a way than runtime discovery through PCI/ACPI/UEFI/etc, but it works. But we're not just talking about need
485.
by mort96 6mo ago
Somehow, this isn't a problem in the desktop space, even though new hardware regularly gets introduced there too which require new drivers.
486.
by mort96 6mo ago
I mean they're right.
487.
by mort96 7mo ago
Different people can understand different parts of the code.
488.
by mort96 7mo ago
A terrifying thought but not implausible. IMO, the world needs more people with a deep understanding of how stuff works, but that's not the direction we're moving in.
489.
by mort96 7mo ago
You can have both 0.1 and 0.2 in the same project, but you really don't want to.
490.
by mort96 7mo ago
I do not care how strong your vibes are and how many claudes you have producing slop and reviewing each others' slop. I do not think vibe coding is appropriate for critical infrastructure. I don't understand why you think telling
491.
by mort96 7mo ago
The availability or lack thereof of compute has absolutely nothing to do with my opinion. More vibe coded tests doesn't fix the problem.
492.
by mort96 7mo ago
Oh hey I recently saw a comment which discussed this exact issue: https://news.ycombinator.com/item?id=47752915
493.
by mort96 7mo ago
Well an EU/EEA thing. And I'm in the EEA, so it applies when I visit The Guardian.
494.
by mort96 7mo ago
I can't even read it because you either have to accept all tracking or pay a subscription fee. Pretty sure that's against the GDPR? Anyway, not a good look.
495.
by mort96 7mo ago
I trust people to understand the code they write. I don't trust them to understand code they didn't write.
496.
by mort96 7mo ago
I disagree. The code itself matters too.
497.
by mort96 7mo ago
I disagree. Thorough testing provides some level of confidence that the code is correct, but there's immense value in having infrastructure which some people understand because they wrote it. No amount of process around your vibe slop
498.
by mort96 7mo ago
We do not need vibe-coded critical infrastructure.
499.
by mort96 7mo ago
By releasing a library with version 1.0, I communicate: "I consider this project to be in a state where it is reasonable to depend on it". By releasing a library with version 0.x, I communicate: "I consider this project to be
500.
by mort96 7mo ago
That page says: > Complete JavaScript execution pipeline from source code parsing to bytecode execution. So it's a bytecode interpreter, not a JIT. It might still be production ready for a bunch of use cases. I may use it as a scrip
501.
by mort96 7mo ago
Versioning is communication. I find it useful to communicate, through using version 0.x, "this is not a production ready library and it may change at any time, I provide no stability guarantees". Why might I release it in that sta
502.
by mort96 7mo ago
No, it's explicitly not. Semver says: > Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable. Cargo is explicitly breaking with Semver by considering
503.
by mort96 7mo ago
Yeah the closest thing you come today is arguably WebKitGTK, which is known for being not exactly great.
504.
by mort96 7mo ago
What do you mean by "production ready" here exactly? In a web browser context, the JS engine is expected to have a high performance optimising JIT compiler. Do the existing Rust JS engines have that?
505.
by mort96 7mo ago
The fundamental problem with Rust versioning is that 0.3.5 is compatible with 0.3.6, but not 0.4.0 or 1.0.0; when major version is 0, the minor takes the role of major and patch takes the role of minor. So packages iterate through 0.x versi
506.
by mort96 7mo ago
Then what?
507.
by mort96 7mo ago
This seems like analysis? "Pat killed Intel’s share price."
508.
by mort96 7mo ago
This looks like a motte-and-bailey. Your original comment, the bailey: "he posted much religious stuff from official Intel accounts". This comment, the motte: "he posted much religious stuff". You could've just said
509.
by mort96 7mo ago
I don't understand what you mean. Stock price has tripled since last August based on Intel finally having a competitive architecture and a competitive process again, no? At least that in combination with various geopolitical circumstan
510.
by mort96 7mo ago
Yes you can write down the result of calculations and all relevant state and then clear the state of the calculator window before doing a new calculation. But why?

More ›