Re:Today, we hacked what we'd set out to hack: the iPhone
by jitl on Friday October 23, 2026 @02:29PM
(#50213393)
> PDF is an old format from a more innocent era
if apple parsed pdf with (js, swift, rust) none of this would be possible. the problem is memory-unsafe code.
Re:Today, we hacked what we'd set out to hack: the iPhone
by Someone on Friday October 23, 2026 @04:26PM
(#50214840)
> if apple parsed pdf with (js, swift, rust) none of this would be possible
Interpreters and compilers can have bugs. Bugs can cause memory safety issues.
Re:Today, we hacked what we'd set out to hack: the iPhone
by tannertech on Saturday October 24, 2026 @09:05AM
(#50220880)
Since when was javascript memory safe
Re:Today, we hacked what we'd set out to hack: the iPhone
by rafram on Saturday October 24, 2026 @02:26PM
(#50223804)
Since it was created.
Re:Today, we hacked what we'd set out to hack: the iPhone
by tannertech on Sunday October 25, 2026 @04:35AM
(#50229456)
Why is it we didn't rewrite coreutils in js a decade ago instead of waiting for rust
Re:Today, we hacked what we'd set out to hack: the iPhone
by rafram on Sunday October 25, 2026 @02:06PM
(#50234273)
Because it’s a high-level interpreted language. Still memory-safe!
Rust is interesting because it’s a low-level language with strong memory safety. That makes it a good fit for projects like coreutils. I’d argue it makes it a bad fit for many other projects that get rewritten in it, though. Not everything actually needs to be in a low-level language with compile-time memory management.
Who am I kidding, I think the PDF format will outlive us.