4 ms·

Has something happened since Apple implemented the no interpreters rule? Didn't Apple outlaw MonoTouch?

by euroclydon 15y ago

sh4na 15y ago
that rule was reversed months ago
- tzs 15y ago
  Also, while it was in effect it was not enforced against apps that used Mono.
  - guelo 15y ago
    Yea, it was all about trying to screw Adobe.
    - melling 15y ago
      Why specifically were they trying to screw Adobe?
      - deleted 15y ago
        [deleted]
      - DrJokepu 15y ago
        That was around when Adobe was planning to ship Flash with an automatic Flash-to-iOS App exporter. Apple tried to (and managed to) stop that from happening.
      - wmf 15y ago
        Flash Player for iOS sucks. But Apple doesn't want developers to forgo developing native apps while waiting for Flash to improve, so they just banned it. It's a clean break.
bad_user 15y ago
MonoTouch generated code is not interpreted.
- euroclydon 15y ago
  Yes, I read that today, but is that a new development from the time of the whole non-Apple-approved language kerfuffle, or have MonoTouch apps always compiled into c/C++/ObjC?
  - ctoshok 15y ago
    monotouch apps were never compiled to c/C++/ObjC. they go straight to native code.
    - mythz 15y ago
      or LLVM
dhimes 15y ago
Thank you for asking this. I came here to ask it. I'm not sure why you were downvoted for it (I assume that's why the comment has been dimmed). Sometimes I don't think I recognize HN. It's a shame, and I hope it doesn't keep you from asking questions here.
- euroclydon 15y ago
  Thanks. People can downvote stuff for silly reasons here, but I've found it's usually pretty easy to know when to take the downvotes as a badge of honor, and when to take them as a genuine learning experience.
- jordan0day 15y ago
  I'm speculating here, but I'm guessing the reason it was downvoted (if it was, I never saw it dimmed) was because the whole "section 3.2.2" thing seems to have been settled around a year or so ago. That is, anyone who was concerned about it being a problem should probably know by now that it ended up being resolved and left MonoTouch unaffected. For a lot of folks I presume it's "old news" and some folks may just think euroclydon is trying to spread FUD.
  - euroclydon 15y ago
    No FUD here. I remember the 3.2.2 thing being news that transcended the realm of just iOS developers, but the resolution, I don't remember that at all. A year, wow, it doesn't seem like that long ago!
    - dhimes 15y ago
      I don't remember it either, probably because I decided that I would just try to make my website work well on mobile and skip the app altogether. Became convinced of this strategy when A decided to take 30% of my sales through an app also (or did they rescind that also?). Anyway, downvoting without comment on something like this is poor.

Has something happened since Apple implemented the no interpreters rule? Didn't Apple outlaw MonoTouch?

sh4na 15y ago

that rule was reversed months ago

tzs 15y ago
Also, while it was in effect it was not enforced against apps that used Mono.
- guelo 15y ago
  Yea, it was all about trying to screw Adobe.
  - melling 15y ago
    Why specifically were they trying to screw Adobe?
    - deleted 15y ago
      [deleted]
    - DrJokepu 15y ago
      That was around when Adobe was planning to ship Flash with an automatic Flash-to-iOS App exporter. Apple tried to (and managed to) stop that from happening.
    - wmf 15y ago
      Flash Player for iOS sucks. But Apple doesn't want developers to forgo developing native apps while waiting for Flash to improve, so they just banned it. It's a clean break.

bad_user 15y ago

MonoTouch generated code is not interpreted.

euroclydon 15y ago
Yes, I read that today, but is that a new development from the time of the whole non-Apple-approved language kerfuffle, or have MonoTouch apps always compiled into c/C++/ObjC?
- ctoshok 15y ago
  monotouch apps were never compiled to c/C++/ObjC. they go straight to native code.
  - mythz 15y ago
    or LLVM

dhimes 15y ago

Thank you for asking this. I came here to ask it. I'm not sure why you were downvoted for it (I assume that's why the comment has been dimmed). Sometimes I don't think I recognize HN. It's a shame, and I hope it doesn't keep you from asking questions here.

euroclydon 15y ago
Thanks. People can downvote stuff for silly reasons here, but I've found it's usually pretty easy to know when to take the downvotes as a badge of honor, and when to take them as a genuine learning experience.
jordan0day 15y ago
I'm speculating here, but I'm guessing the reason it was downvoted (if it was, I never saw it dimmed) was because the whole "section 3.2.2" thing seems to have been settled around a year or so ago. That is, anyone who was concerned about it being a problem should probably know by now that it ended up being resolved and left MonoTouch unaffected. For a lot of folks I presume it's "old news" and some folks may just think euroclydon is trying to spread FUD.
- euroclydon 15y ago
  No FUD here. I remember the 3.2.2 thing being news that transcended the realm of just iOS developers, but the resolution, I don't remember that at all. A year, wow, it doesn't seem like that long ago!
  - dhimes 15y ago
    I don't remember it either, probably because I decided that I would just try to make my website work well on mobile and skip the app altogether. Became convinced of this strategy when A decided to take 30% of my sales through an app also (or did they rescind that also?). Anyway, downvoting without comment on something like this is poor.