I agree with you, but I would suggest your wording is very
sloppy, leaving you
open to attacks from trolls.
Some programs may be ported to
Android from
other platforms. If the vocabulary is changed, these
programs
won't port without being rewritten.
There are two
definitions for "porting" in my
understanding. That can simply mean recompiling
the source
code as is on another platform, or it can mean modifying
parts of
the source code that are system dependent first
before recompiling, necessary
if there are system
dependencies. There are no programs that can be ported to
Android by simply recompiling the code. Whatever you try to
port will need
modifications to the source code to some
extent. So then you say "If the
vocabulary is changed, these
programs won't port without being rewritten." but
a troll
will say, "The source code requires modification anyway.
While you are
at it, you could simply change the
vocabulary."
Also, some
programs are written to run on
every platform, or at least as many platforms as
possible.
This is the "write once run anywhere" feature of Java. Does
this
count as functionality?
A troll will say, "Android doesn't
have this
functionality." and he will be correct. Android doesn't have
this
functionality at the program level."
Having a different
vocabulary for Android
will definitely break this because Android programs
won't
run elsewhere and Java programs won't run on Android.
A troll will say "Android programs and Java programs are
not
interchangeable - ie: one won't run on the other
platform." again negating your
comment.
In the end, with the sloppy wording you use, a troll will
rip
your comment to shreds. The problem is you should be
using the word "modules"
or "classes" or "methods" or
"snippets" or anything but "programs".
You
begin your comment by asking the question "Does
compatibility count as
functionality?" I say yes, but
compatibility is not at the level of the
program. It is at
the level of code reuse. Programmers rarely start a project
from scratch - at least - I never do. We always begin with
bits and pieces of
other programs we have written
previously, and start with some framework we
wrote for a
similar program previously. We will take that framework, for
example, and gut it, then start copy and pasting classes,
methods, functions,
headers, modules, whatever we have. Then
from that raw material we will slowly
work it into a new
program, finally adding all new code, classes, modules,
whatever we need.
We can take pieces of previously written Java
programs and port them to Android, and yes, this level of
compatibility counts
as functionality. [ Reply to This | Parent | # ]
|