Menu
▾
▴
Re: [xmlvm-users] Feedback from Apple regarding XMLVM and the iPhone SDK license agreement
|
From: Joris V. <jbv...@gm...> - 2010-04-18 17:45:17
|
Ok, I think I'm beginning to understand what's going on here. I'm not really familiar with jailbroken compilation, but from what I've seen, is that some apps are compiled with custom gcc buildscripts. I can understand why apple would not want to support this. I also understand why apple would rather not have scripting languages/vms.. There's a reason why they don't do garbage collection on the iPhone. My assumption is that codegeneration tools will be allowed, also because it's a good thing for the iPhone ecosystem. Not everybody can create the same quality stuff in all languages / tools. There's a reason why tools and engines are used. Using middleware should improve overall quality, as there is less to focus on. This is of course well known. The problem Apple is facing, is the huge number of low quality apps. If you require to use Apple's tools, you will only have: * Developers that already worked with apple tools//xcode/objc * Developers that won't go for the platform * Developers that will take the effort to learn the platform * Developers that will learn the platform, but only to get up and running, and therefore missing a lot of the APIs.. resulting in the same 'bad' software. This, however, will NOT improve app quality. A lot of the apps available are created by one-man developers, and one of the things most developers can't do is design. If you look at normal software, it's the same story, and low quality software will be less known than good quality. There's one big difference. Normal software relies on google, and apple's appstore relies on releasedate, ratings, and weekly popularity. This model is nice for trends, but not for general apps. The same has been true for desktop software. How many people still use zdnet or whatever to find new software? Most people use software recommended by friends, and occasionally software recommended by blogs like lifehacker. Apple needs to realize that it can't control this. They can provide tools to support, but at this point they're inadequate. The appstore as a distribution platform IS a good thing. It provides users and developers an easy way to get and sell software. Apple can improve their appstore by having a searchable featured list, buddylist / recommendations, better searchengine. Though it still won't be good enough.. Maintaining a list of good software is hard (and next to impossible) work. So far my rant ;) On Sun, Apr 18, 2010 at 09:29, Gergely Kis <ger...@ma...> wrote: > Hi, > > I hope this means that Apple will allow XMLVM to exist, and it is not the > independent, unofficial thoughts of a sales rep guy, who is "not a > programmer". > > I don't know if he got the links to the xmlvm.org website + the Google Tech > Talk slides of Arno, but there are nice diagrams in each to make it clear > what XMLVM does. > > I would also like to suggest to separate the Android API library as an > optional component. > > In fact, we are not using the Android library in our "real" projects. We > code directly against the UIKit Java bindings. Thus the compiled > applications are in essence native iPhone applications that use only legal > Objective-C constructs (categories, public iPhone API). > > With the Android API they could argue that the marriage of the different UI > toolkits will lead to inferior user experience. They could also see XMLVM as > a threat of a flood of Android apps, the same way they saw a threat in Flash > apps. > > In reality, you will have to change the UI design of your Android app anyway > to match the Human Interface Guidelines, and the differences in the hardware > (e.g. the absence of a "Back" button). So it makes more sense to keep the > business layer / backend of the application platform independent, and code > the user interface specifically for the platform (iPhone and Android > respectively) > > Maybe it would make sense to create different diagrams which explains the > above, and does not make the Android API a central use case of XMLVM. > > So I would like to ask that when you communicate with the "Apple Guy", you > try to make it clear that XMLVM is not an Android "compatibility layer" > (language from section 3.3.1). It is a "pre-processor" (term from the > DaringFireball blog posting) which creates Objective-C code that has the > same properties like any hand-written Objective-C code. > > Best Regards, > Gergely > > 2010/4/18 Wolfgang Korn <wol...@xm...> >> >> The sentence about alternatives - that's exactly what we are doing, >> isn't it. >> >> -- Wolfgang >> >> Sent from my iPhone >> >> On 18.04.2010, at 03:48, Panayotis Katsaloulis >> <pan...@pa...> wrote: >> >> > I don't get it. >> > Probably this guy needs to be better informed. >> > >> > 1. Someone should tell him that XMLVM *could* be used to provide >> > iPhone-only applications. >> > >> > 2. About this part: >> >> An alternative could be creating a tool that can convert software >> >> applications from other platforms and then utilizes the compilers for >> >> the iPhone to actually create the application. >> > >> > Isn't that *exactly* what XMLVM does? >> > >> > >> > --- >> > --- >> > --- >> > --------------------------------------------------------------------- >> > Download Intel® Parallel Studio Eval >> > Try the new software tools for yourself. Speed compiling, find bugs >> > proactively, and fine-tune applications for parallel performance. >> > See why Intel Parallel Studio got high marks during beta. >> > http://p.sf.net/sfu/intel-sw-dev >> > _______________________________________________ >> > xmlvm-users mailing list >> > xml...@li... >> > https://lists.sourceforge.net/lists/listinfo/xmlvm-users >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> xmlvm-users mailing list >> xml...@li... >> https://lists.sourceforge.net/lists/listinfo/xmlvm-users > > > > -- > Kis Gergely > MattaKis Consulting > Email: ger...@ma... > Web: http://www.mattakis.com > Phone: +36 70 408 1723 > Fax: +36 27 998 622 > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users > > |
