Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.mobile.android > #37553

Re: Facetime on Android

From Frank Slootweg <this@ddress.is.invalid>
Newsgroups comp.mobile.android
Subject Re: Facetime on Android
Date 2017-01-08 17:00 +0000
Organization NOYB
Message-ID <edf9ghFfar7U1@mid.individual.net> (permalink)
References (8 earlier) <060120171548549579%nospam@nospam.invalid> <edcvbjFslbhU2@mid.individual.net> <070120171511544127%nospam@nospam.invalid> <edd4u3Fu1lhU1@mid.individual.net> <070120171823082576%nospam@nospam.invalid>

Show all headers | View raw


nospam <nospam@nospam.invalid> wrote:

[Non-explantion why a wall isn't one deleted.]

> you're also showing just how much of hypocrite you are in that there
> are a lot of apps that are *only* on android or *only* on windows, with
> no option for mac or ios users. in your world, that would be a wall,
> which you conveniently ignore.

  First of all, I never claimed that Google or/and Microsoft are
anything even remotely close to perfect, quite the contrary (if you've
been paying any attention). Android/Google sucks, but they're the only
option in the price range I'm willing to pay for a throw-away device
like a smart-phone/tablet. And I'm using a laptop *despite* Windows (and
for the same price argument).

  Having said that, ...

  Care to give some actual examples? And ones which are relevant to the
topic at hand, i.e. (human) communication between devices.

[...]

> why doesn't google port android to iphones and ipads? 

  That's not what knowledgeable people would call a 'port', because it
would require a rewrite of all the hardware dependent stuff. Assuming
it's at all possible, given CPU architecture, etc.. (Note that, despite
what some people think, Android is not Linux.)

> the ios kernel is open source, as is quite a bit more, so they have a
> head start.

  Sorry, but you seem to be out of your league. The iOS kernel would be
mostly useless, because what's needed is an *Android* kernel for
iHardware.

> why doesn't another company port android to existing ios devices?

  Because it's a *gigantic* undertaking. Absolutely incomparable with
porting FaceTime to other platforms.

> that would be a *lot* cheaper than designing and building a new
> android phone.

  You're kidding, right!? Designing and building a new Android phone is
peanuts, compared to rewriting Android for iHardware.

  Not that the two can be compared, because they require totally
different expertise, people, equipment, etc..

[...]

> also note that there are licensing fees to use parts of android, which
> is a wall. some of those noname android devices do not have the play
> store, which means a lot of apps aren't directly available to them. yet
> another wall.

  Every one needs to pay licences and other fees all the time, but more
importantly, such a financial wall is, as you (should) know full well,
not the kind of wall which is meant when one talks about a "walled
garden".

Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Facetime on Android Stijn De Jong <stijndekoning@nlnet.nl> - 2016-12-31 07:36 +0100
  Re: Facetime on Android Joerg Lorenz <hugybear@gmx.ch> - 2016-12-31 09:25 +0100
    Re: Facetime on Android Stijn De Jong <stijndekoning@nlnet.nl> - 2016-12-31 20:17 +0100
  Re: Facetime on Android tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-12-31 04:07 -0500
    Re: Facetime on Android Stijn De Jong <stijndekoning@nlnet.nl> - 2016-12-31 20:17 +0100
  Re: Facetime on Android Chris <ithinkiam@gmail.com> - 2017-01-06 08:36 +0000
    Re: Facetime on Android nospam <nospam@nospam.invalid> - 2017-01-06 08:58 -0500
      Re: Facetime on Android Piet <www.godfatherof.nl/@opt-in.invalid> - 2017-01-06 16:20 +0100
        Re: Facetime on Android nospam <nospam@nospam.invalid> - 2017-01-06 11:03 -0500
          Re: Facetime on Android Frank Slootweg <this@ddress.is.invalid> - 2017-01-06 19:48 +0000
            Re: Facetime on Android nospam <nospam@nospam.invalid> - 2017-01-06 15:16 -0500
              Re: Facetime on Android Frank Slootweg <this@ddress.is.invalid> - 2017-01-06 20:40 +0000
                Re: Facetime on Android nospam <nospam@nospam.invalid> - 2017-01-06 15:48 -0500
                Re: Facetime on Android Chris <ithinkiam@gmail.com> - 2017-01-07 11:08 +0000
                Re: Facetime on Android nospam <nospam@nospam.invalid> - 2017-01-07 13:06 -0500
                Re: Facetime on Android Frank Slootweg <this@ddress.is.invalid> - 2017-01-07 19:54 +0000
                Re: Facetime on Android nospam <nospam@nospam.invalid> - 2017-01-07 15:11 -0500
                Re: Facetime on Android Chris <ithinkiam@gmail.com> - 2017-01-07 22:57 +0000
                Re: Facetime on Android nospam <nospam@nospam.invalid> - 2017-01-07 18:23 -0500
                Re: Facetime on Android Frank Slootweg <this@ddress.is.invalid> - 2017-01-07 19:54 +0000
                Re: Facetime on Android nospam <nospam@nospam.invalid> - 2017-01-07 15:11 -0500
                Re: Facetime on Android Frank Slootweg <this@ddress.is.invalid> - 2017-01-07 21:29 +0000
                Re: Facetime on Android nospam <nospam@nospam.invalid> - 2017-01-07 18:23 -0500
                Re: Facetime on Android tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-08 00:48 -0500
                Re: Facetime on Android Frank Slootweg <this@ddress.is.invalid> - 2017-01-08 17:00 +0000
                Re: Facetime on Android nospam <nospam@nospam.invalid> - 2017-01-10 21:41 -0500

csiph-web