|
|
Sponsored Content
Operating Systems
Linux
Android
Will You Move to an Android Phone or Tablet?
Post 302484617 by Neo on Sunday 2nd of January 2011 03:36:04 AM
01-02-2011
Administrator
A Java paradigm on Linux for mobile applications is very powerful. It is just a matter of time when Android for tablets comes out (scheduled for 1Q 2011) and we are only seeing the beginning.
There is minimal overall computing difference between writing a C program and compiling it, versus writing a Java program and compiling it. The main difference is that, for the foreseeable future, Android Java programs will be developed "off platform" and then installed (on a table, on a mobile), whereas Linux/Unix can easily develop and compile "on platform".
However, this will change over time, especially as tablets become more mainstream, larger screens, external bluetooth keyboards and mice, etc. Smart phones and tablets are amazing. We are only in the early stages of a computing revolution, where much of what we need for personal and business communications is in tables and phones.
FWIW, I will buy a new Android tablet after the release of Android-for-tablets. I was going to get one this year, a Galaxy Tab, but decided to wait until 2011 after Android 3.0 is adopted for tables (or at least a version of Android for tablets). I would develop some apps on Android now, but I still have a legacy OSX PPC on my desk which is not very suitable (and not supported).
PS: Yes, I have some some development in Java when I worked as a principle architect large s/w company in Palo Alto. I have worked in both Java and C in the past; but mostly in PHP these days
---------- Post updated at 08:36 ---------- Previous update was at 08:28 ----------
I don't see anything fundamentally wrong with a GUI on a platform designed to be manipulated with our finger and not a mouse or traditional keyboard, BTW.
It is simply a different user interface model. It is a model which many people like, considering smart phones and tables were the hottest gadgets on the market in 2010 and destined to be even hotter in 2011.
There is minimal overall computing difference between writing a C program and compiling it, versus writing a Java program and compiling it. The main difference is that, for the foreseeable future, Android Java programs will be developed "off platform" and then installed (on a table, on a mobile), whereas Linux/Unix can easily develop and compile "on platform".
However, this will change over time, especially as tablets become more mainstream, larger screens, external bluetooth keyboards and mice, etc. Smart phones and tablets are amazing. We are only in the early stages of a computing revolution, where much of what we need for personal and business communications is in tables and phones.
FWIW, I will buy a new Android tablet after the release of Android-for-tablets. I was going to get one this year, a Galaxy Tab, but decided to wait until 2011 after Android 3.0 is adopted for tables (or at least a version of Android for tablets). I would develop some apps on Android now, but I still have a legacy OSX PPC on my desk which is not very suitable (and not supported).
PS: Yes, I have some some development in Java when I worked as a principle architect large s/w company in Palo Alto. I have worked in both Java and C in the past; but mostly in PHP these days
---------- Post updated at 08:36 ---------- Previous update was at 08:28 ----------
I don't see anything fundamentally wrong with a GUI on a platform designed to be manipulated with our finger and not a mouse or traditional keyboard, BTW.
It is simply a different user interface model. It is a model which many people like, considering smart phones and tables were the hottest gadgets on the market in 2010 and destined to be even hotter in 2011.
|
|
4 More Discussions You Might Find Interesting
1. Android
I just upgraded to Android 2.2 from 2.1. The GPS issue that was troublesome in 2.1 seems to have been fixed. Some of web browsing seems faster, but it could just be my connection is better today ;) Flash works in some browsers but not very good and it is too slow for Flash apps designed for... (0 Replies)
Discussion started by: Neo
0 Replies
2. What is on Your Mind?
Currently in the process of looking for a tablet. Which one is best? Thanks Benjamin Mauerberger (9 Replies)
Discussion started by: hlinks12
9 Replies
3. Solaris
I'm trying to sync/transfer files from my UNIX box and Android Phone and vice versa.
I know that Android Phones show up seamlessly (mostly) in Linux given their incestuous relationship.
Is there a way to do it in UNIX or more specifically in Solaris 11.3 (i86)?:confused:
I haven't found one... (2 Replies)
Discussion started by: Nostradamus1973
2 Replies
4. Emergency UNIX and Linux Support
thanks (6 Replies)
Discussion started by: jgt
6 Replies
LEARN ABOUT DEBIAN
abootimg
ABOOTIMG(1) General Commands Manual ABOOTIMG(1) NAME
abootimg - manipulate Android Boot Images. DESCRIPTION
Tool to read/write/update android boot images SYNOPSIS
abootimg -i <bootimg> abootimg -x <bootimg> [<bootimg.cfg> [<kernel> [<ramdisk> [<secondstage>]]]] abootimg -u <bootimg> [-c "param=value"] [-f <bootimg.cfg>] [-k <kernel>] [-r <ramdisk>] [-s <secondstage>] abootimg --create <bootimg> [-c "param=value"] [-f <bootimg.cfg>] -k <kernel> -r <ramdisk> [-s <secondstage>] OPTIONS
-i print boot imgage informations -x Extract a boot image -u Update a boot image --create Create a boot image Options for extracting boot images bootimg Existing bootimage to use bootimg.cfg Name for the bootimg.cfg file, defaults to bootimg.cfg kernel Name for the kernel image, defaults to zImage ramdisk Name for the ramdisk image, defaults to initrd.img secondstage Name for the second-stage image, defaults to stage2.img Options for updating and creating boot images bootimg Existing bootimage to use -c param=value Existing bootimage to use -f <bootimg.cfg> Update bootimg.cfg with the named file -k <kernel> Update kernel with the named file -r <ramdisk> Update ramdisk with the named file -s <secondstage> Update secondstage image with the named file ABOOTIMG(1)