5 ms·
I wasn't even aware that you were allowed to ship Rust code in iOS apps, I thought that Apple had a whitelist of allowed languages? EDIT: And for those interes
by kibwen 10y ago
I wasn't even aware that you were allowed to ship Rust code in iOS apps, I thought that Apple had a whitelist of allowed languages?
EDIT: And for those interested, you might want to check out Rust's recent inclusion in a AAA title: https://www.reddit.com/r/rust/comments/69s225/rust_makes_it_into_a_aaa_video_game_as_an_art/ https://www.reddit.com/r/rust/comments/69s225/rust_makes_it_... :P
- wyldfire 10y agoReally? How do they know what the representation of the object code was before compilation? Seems like if they had a whitelist it would be difficult to enforce.
- kibwen 10y agoNote that I've obviously never written an iOS app, but I figured that Apple required you to submit the source of your app for their auditing process. Which sounds extreme, but this is Apple we're talking about. :)
- adrianmalacoda 10y agoThere was indeed a rule at one point that apps had to be written in C, C++, or Objective-C. This was allegedly implemented in order to ban cross-compilers such as Flash compiler[0]. Presumably they would either require the source code to verify this, or inspect the compiled binary for some identifying feature. However, these rules don't exist in the current version of the guidelines[1]. [0] http://daringfireball.net/2010/04/iphone_agreement_bans_flash_compiler http://daringfireball.net/2010/04/iphone_agreement_bans_flas... [1] https://developer.apple.com/app-store/review/guidelines/ https://developer.apple.com/app-store/review/guidelines/
- Impossible 10y agoThis rule got so much press 7 years ago that it will be one of those "truths" about a platform that never dies on internet forums, that and the Playstation platforms using OpenGL as their primary API...
- jhasse 10y agoI have submitted an app in the past and no, you don't have to submit the code.
- bluejekyll 10y agoThe biggest problem I faced with Rust and macOS/iOS is related to Apple's requirement for bitcode on all submitted code to the App Store for Watch and appleTV applications. This internal Rust discussion focuses on it for more details: https://github.com/rust-lang/rust/issues/35968 https://github.com/rust-lang/rust/issues/35968 This gist is that Apple is requiring bitcode, but isn't giving easy access to the LLVM version they use for their own tools. This means there's not a path forward to support bitcode generation from Rust that would align with Apple's requirements. This currently only effects iOS on Watch and TV, meaning you can easily target macOS and iPhone without issue, but I fear that the writing is on the wall.
- nebabyte 10y agoI continue to be amazed that apple is not considered as having a monopoly on "stores for apple devices". These are exactly the kind of archaic requirements that would be a nonstarter or otherwise kill market support for a store given any actual competition. Instead, they are able to leverage it to try and push their 'approved' languages and developer environments - furthering anticompetitive lock-in. Apple making money from selling devices (or even distributing "at a loss" devices which they benefit from having exist so they can better act as software vendors) and them making money from their store are two separate revenue streams, after all.
- self-diversity 10y agoI imagine it would be easier to accept your assertion of anti-competitive behavior if it weren't trivial to completely ignore Apple for your phone needs, or if there were some sort of Constitutional right guaranteeing you the Apple phone of your dreams
- eridius 10y ago"products made by one brand" isn't a category of products. If they're the only brand that makes products for a particular category, then they're a monopoly, but you cannot simply define a category as "stuff made by that company", because by that logic, every company is a monopoly on stuff made by them.
- sqeaky 10y agoRust as an art asset! The dimly lit room, the red glowing Rust code on the wall, the main character with a large gun and the commenter saying that requires and unsafe block. The Reddit comments are great. Edit - Could you tell me why you downvoted me. This wasn't even the slightest bit argumentative, so I am not sure who I angered.
- lobster_johnson 10y agoI didn't downvote you, but I also don't understand what your comment even means. Dimly lit room... what? What Reddit discussion are you referring to? What does your comment have to do with writing games in Rust?
- ekimekim 10y agoThey're commenting on the link in the GP about "Rust's recent inclusion in a AAA title" (some rust code is used as text in a generic 'computer code' image)
- sqeaky 10y agoThis tells me why I got downvotes, I replied to the wrong comment. The game wasn't written in rust, is was used in a texture and drawn on a wall.
- steveklabnik 10y agoThe game that's the subject of the OP is written in Rust. The one in the Reddit thread linked elsewhere was only a texture.
- sqeaky 10y agoBut I think we can all agree that if we are programming a gun there should be an unsafe block.
- eridius 10y agoFor a brief time they had restrictions on the languages you could use. That was a reaction to Adobe shipping a tool to compile your Flash source into an iOS app. But that didn't last very long. That said, if you're dynamically interpreting code at runtime that was downloaded from the internet, you're only allowed to do that using JavaScriptKit. You cannot, for example, embed the Lua interpreter and then interpret code downloaded (but code in your app bundle is fine).