@mdhughes I agree. Just saying, it's not fear mongering to suggest that you really have no leg to stand on if you clearly violate the rule.
@mdhughes You seem to be saying, don't worry about clearly violating the letter of the agreement because they won't enforce it against you.
@mdhughes RegexKitLite is by definition a translation/compatibility layer atop the APIs in the SDK. (And Engelhart warns about this.)
@danielpunkass What was his complaint? Seems to me that if you liked MarsEdit 2 you'd like 3, too.
@tristan Checkout, Lightroom, Dropbox, Acorn (parts),...
@mdhughes Also, if you parse anything other than data, then your app includes code not written in C/JavaScript, so you fail that way, too.
@mdhughes Unrelated to exposing it to the user. If you use a parser generator the parser code wasn't "originally written" in C.
@mdhughes Unless you want to use a parser, or RegexKitLite, or any number of tools that reasonable people would consider proper.
@incanus77 Yes, that's a fine solution if you want to build Mac apps that wouldn't benefit from mobile versions or tie-ins.
@natevw If more join, there will be more potential apps that people won't know about and so can't miss.
@mikeash Yes, I see it as proof of moving in the wrong direction, but I guess most people are happy that the reviewing times have decreased.
@mikeash The best argument I can see for not caring is that 3.3.1 is just a named subset of the arbitrary power that already existed.
@mikeash Well, I think most people see it as just a ban on crummy apps and developers who can't be bothered to learn real languages.
Not sure what happened, but FogBugz is once again working properly with Safari and other WebKit browsers. Thanks for filling in, Camino.