Hacker News Reader

Comment by saagarjha | Hacker News Reader

Shipping unsafe C++ is easier on Apple platforms than Rust. This seems unlikely to change anytime soon.

Is it? I wrote a pure rust iOS app recently. It uses native controls, and looks and feels great. iOS and iOS-sim are both very well supported targets by the rust compiler.

You’re not shipping code as part of Safari

You're moving the goalposts. You said:

> Shipping unsafe C++ is easier on Apple platforms than Rust.

... Which seems false.

I can easily believe that apple might not have rust tooling in their Safari build system. But that doesn't mean rust has poor support for apple platforms.

No, you're reading what you want out of my comment. The context of this thread was very clearly browser support of JPEG XL, not your apps.

Chrome and Firefox are shipping lots of rust code today. They work great on Apple platforms. They’re even both planning to use rust for JPEG XL.

What is your claim, exactly? Because as far as I can tell, there’s nothing stopping safari from using rust if they wanted to.

My claim is that there is quite a bit stopping Safari from using Rust ;)

Like what? I'm unconvinced.

You will note that Apple has not shipped any Rust in their OS

I do not feel so.

Not only Rust does C API, but Objective-C the way it allows to call Apple platform and call Apple compatible functions back.

Also well integrated Rust programs(with platform calls and low level hardware access) are well compiled without Apple SDK.

3-4 kicking Rust solutions are easy findable in this area.

Just because it is possible or even easy does not mean it will happen.

Reply on news.ycombinator.com