有没有Objective-C和Java或iPhone和Android之间的巨大差异?差异、巨大、Java、Objective

2023-09-12 11:08:04 作者:余生望你指教

编辑:我不好,我的意思的Objective-C,而不是C#。某些原因,我把它变成我的头是C#所使用的iphone。所以答案为C#是伟大的,谢谢,但吗更有有点不相干,我们对此深感抱歉。

My bad, I meant objective-c, not c#. Some reason I got it into my head it was c# the iphone used. So the answers for c# were great, thanks, but theyre a bit irrelevant, sorry about that.

我当时一看却找不到任何答案这一点,虽然有少数回答它的部分缩短的问题。之间的小团体,我们计划做在iPhone和Android的2个独立的大部分一些工作,但互相帮助,并与一些球员做他们之间的图形工作分裂。

I've had a look but can't find anything that answers this, though a few have shortened the question by answering parts of it. Between a small group, we were planning on doing some work on iPhone and Android, the 2 seperate for the most part but helping each other out, and with some guys doing graphics work split between them.

但是,我们想搬东西两者之间,不一定是应用程序,也许只是有用的类或某事的可能性。纵观Objective-C和Java中,他们似乎有关于最大的障碍将是系统界面的东西相同的功能,所以我们不知道是否,如果我们创建的每个系统上的抽象通过这些,使他们可以给予相同的输入(其中,除非我很错了也不会放太多的应变系统?),会有书面的东西Objective-C和Java的,比在软件开发工具包方法的位置差之间进行转换的任何问题?还是有关键特征或东西在一种语言,其他没有,我们已经错过了,这将意味着这样做会被重写从头开始。唯一的办法

But we were thinking about the possibilities of moving things between the two, not necessarily apps, maybe just useful classes or something. Looking at objective-c and Java, they seem to have about the same features that the biggest obstacle would be system interface stuff, so we were wondering whether, if we created an abstraction over these on each system so they could be given the same input (which unless I'm wrong wouldn't put too much strain on the system?), would there be any problems in writing something to convert between objective-c and Java, worse than the locations of methods in the sdks? Or are there key features or something in one language that the other doesn't have which we've missed that would mean the only way to do it would be rewriting from scratch.

推荐答案

我不会浪费时间去寻找iOS和Android之间的共性。

I wouldn't waste time trying to find commonality between iOS and Android.

跨平台几乎总是浪费时间和资源,除非跨平台能力,是中央的应用程序功能。即对于具有定制的操作系统和工作非常紧密地与硬件平台如iPhone和Android尤其如此。

Cross-platform is almost always a waste of time and resources unless the cross-platform capability is central to the apps functioning. That is especially true for platforms such as iPhone and Android which have custom OS and work very tightly with the hardware.

跨平台开发环境中增加而不是降低复杂性长期性的。是的,这听起来很整洁,但通常你得到你想要轻松的90%,然后你打一个路障,破坏你的节余,然后开始把你的洞。只是有很多妥协和方形钉塞进圆孔。

Cross-platform development environments add rather than reduce complexity long term. Yeah, it sounds neat but usually you get 90% what you want easily and then you hit a roadblock that destroys all the savings you made and then starts putting you in the hole. There are simply to many compromises and square pegs jammed into round holes.

除非你的应用程序在理论上可以工作,从一个普通的网页,跨平台是不适合你。

Unless your app could in theory work from a generic web page, cross-platform is not for you.

在Objective-C和Java的具体情况,尽管Java是由Objective-C的后裔,他们没有现代化的互操作性。不能使用code,从一个在另一个。

In the specific case of Objective-C and Java, although Java is descended from Objective-C they have no modern interoperability. You can't use code from one on the other.

您应该花时间去学习每个平台的特定的API。有没有捷径可走。

You should spend the time to learn each platform's specific API. There are no shortcuts.

 
精彩推荐
图片推荐