目前我们公司有一个巨大的推动跨平台（iOS和Android）的发展。 Appcelerator的钛正在考虑（和似乎是正在被考虑的唯一的东西）来实现，无需额外的开发时间多平台开发。

At our company there is a huge push for cross-platform (iOS and Android) development. Appcelerator Titanium is being considered (and seems to be the only thing that's being considered) to achieve multi-platform development without extra development time.

这里的每个人能想到的理由来使用钛。对于反对使用钛的原因，我的猜到的由钛所产生的原生的应用程序的性能可能不是不如用Objective-C适用于iOS的应用程序。如何显著会的区别是什么？是否有其他原因不能使用钛（或同等学历）？

Everyone here can think of reasons to use Titanium. For reasons against using Titanium I guess the performance of the resulting "native" app from Titanium may not be as good as an app written in Objective-C for iOS. How significant would the difference be? Are there other reasons to not use Titanium (or equivalent)?

注意：我可以写钛，但原因可能不仅是钛的具体而已。支持所有原因编码平台的语言（如Objective-C中，Java的）资格。

Note: I may write Titanium but reasons may not only be Titanium specific only. All reasons in support for coding in platform language (e.g. Objective-C, Java) qualify.

推荐答案

优点：

坏消息：

苹果一直拒绝一些应用程序钛因调用私有API而Appcelerator的没有回应请求帮助，也更新了自己的SDK。 http://developer.appcelerator.com/question/123785/app-has-bee-rejected-by-non-public-api

本地窗口小部件被使用，但只是名义上：有一层 他们和你的code之间的逻辑和抽象;而这层 改变他们的行为，并降低他们的速度。所不同的是 可见的展示应用程序。

"Native Widgets" are used, but only nominally: there's a layer of logic and abstraction between them and your code; and this layer changes their behavior and reduces their speed. The difference is visible in the Showcase apps.

API文档是永远过时。 （无进程刷新）。

API docs are perpetually out of date. (no process for refreshing).

一个维基的创建，这是越来越过时。编辑只 允许员工。

A wiki was created, which is becoming out of date. Editing only allowed for employees.

Github上项目并没有使维基。

Github projects do not have wiki enabled.

Appcelerator的不是的真正的开源：他们不接受的捐款来自社会各界：本 在GitHub titanium_mobile项目有开拉的长长的清单 请求。

Appcelerator isn't true open source: they do not accept contributions from the community: The titanium_mobile project on github has a long list of open pull requests.

帮助论坛软件有很多的技术和放大器;设计缺陷。

The help forum software has many technical & design weaknesses.

电子邮件通知往往不起作用。

Email notifications from the help forum often do not work.

很少的工作人员在回答的Q＆放的问题;一个论坛。一直没见过 在几个月。

Staff rarely answers questions in the Q&A forum. Haven't been seen in months.

搅局者中的所有的小差距不断出现：

Showstoppers appear continuously in "all the little gaps":

在iPhone 4上正确显示图像

Correctly displaying images on the iPhone 4

在滚动列表中正确加载图像

Correctly loading images in a scrolling list

虽然平台并同时支持iOS和Android， 库/框架不。很多运行测试（如果/那么的） 需要的应用程序，将工作在Android和iPhone。

Although the platform does simultaneously support iOS and android, the library/framework does not. A lot of runtime testing (if/then's) is needed in apps that will work on android and iphone.

不断推出新产品，但没有固定的现有产品 和网站的问题。 新的产品，而在测试版发布 并发布候选阶段。

Continually releasing new products but not fixing existing products and website problems. The "new" products are announced while in beta and release candidate phases.

聊天与销售应用程序不参加的。

"Chat with Sales" app not attended to.

Appcelerator的不取下来过时的培训视频。

Appcelerator does not take down outdated training videos.

伸展真相，诱饵和开关，定价：30％的销售 只适用于每年的会员，不是一个月至三个月。该博客 帖子＆功放;营销材料没有说明这一点。只有在结帐的 此图所示。

Stretching the truth and bait-and-switch with pricing: a 30% sale only applies to yearly memberships, not month-to-month. The blog posts & marketing materials do not state this. Only upon checkout is this shown.

[2011/8/13看]另一种方式Q＆放大器; A论坛被打破：的顺序 结果一个搜索丢弃：结果的每一页排序其点击率 从最旧到最新的，在页面的底部。转到下一个 结果（即51-100），并再次的页面，1岁的点击率是 首先，用6周大的底部。

[Seen 8/13/2011] Another way in which Q&A forums are broken: The order of results for a search is trashed: each page of results orders its hits from oldest to most recent, at the bottom of the page. Go to the next page of results (i.e. 51-100), and again, the 1-year-old hits are first, with 6-weeks-old at the bottom.

我未答复的问题：

[七解答Q＆放大器; A问题没有显示：我不想亲自由Appcelerator的工作人员确定 并获得低于标准杆的治疗。]

[Seven unanswered Q&A questions not shown: I don't want to be personally identified by Appcelerator staff and receive sub-par treatment.]

结果：

我花很多时间试图发现在没有文档的API，和黑客发现解决方法。这浪费时间，并且会被更好地用简单的学习，使X code和应用程序; Objective-C的。

Am spending many hours trying to discover an API in the absence of documentation, and hacking to discover workarounds. This time is wasted, and would have been better spent simply learning to make apps in XCode & Objective-C.