La vérité est sur les blogs des idiots, c'est connu!
Tu peux nous rappeler l'adresse du tiens?
A+ JF
user
P4nd1-P4nd4 wrote:
Il ne supporte même PAS LE PLUG AND PLAY !
http://laforge.gnumonks.org/weblog/2009/11/04/
GIGA LOL pour l'ogre ANDROID, qui devait faire d'une bouchée de la chair à patée de WIndows
HHOOOOHHOHOHO HIHIHIHIHIHHIIIHIIHIIIHI UHUH
c'est pour dire que android n'est pas linux et que google a jete les meilleurs parts dans GNU/linux ...
A lire: Android Mythbusters (Matt Porter)
Some weeks ago I was attending Embedded Linux Conference Europe. My personal highlight at this event was the excellent Android Mythbusters presentation given by Matt Porter.
As you may know, Matt Porter was heavily involved in the MIPS and PPC ports of Android, so he and his team have seen the lowest levels of Android, more and deeper than even cellphone manufacturers ever have to look into it.
The slides of his presentation are now available for download. I would personally recommend this as mandatory reading material for everyone who has some interest in Android.
The presentation explains in detail why Android is not what most people refer to when they say Linux. What most people mean when they say Linux is the GNU/Linux system with it's standard userspace tools, not only the kernel.
The presentation shows how Google has simply thrown 5-10 years of Linux userspace evolution into the trashcan and re-implemented it partially for no reason. Things like hard-coded device lists/permissions in object code rather than config files, the lack of support for hot-plugging devices (udev), the lack of kernel headers. A libc that throws away System V IPC that every unix/Linux software developer takes for granted. The lack of complete POSIX threads. I could continue this list, but hey, you should read those slides. now!
Just one more practical example: You cannot even plug a USB drive to an android system, since /dev/sd* is not an expected device name in their hardcoded hotplug management.
Executive summary: Android is a screwed, hard-coded, non-portable abomination.
I can't wait until somebody rips it apart and replaces the system layer with a standard GNU/Linux distribution with Dalvik and some Android API simulation layer on top. To me, that seems the only way to thoroughly fix the problem...
-- -- What's on Shortwave guide: choose an hour, go! http://whatsonshortwave.tk 700+ Radio Stations on SW http://swstations.tk 300+ languages on SW http://radiolanguages.tk
P4nd1-P4nd4 wrote:
Il ne supporte même PAS LE PLUG AND PLAY !
http://laforge.gnumonks.org/weblog/2009/11/04/
GIGA LOL pour l'ogre ANDROID, qui devait faire d'une bouchée de la
chair à patée de WIndows
HHOOOOHHOHOHO HIHIHIHIHIHHIIIHIIHIIIHI UHUH
c'est pour dire que android n'est pas linux et que google a jete les
meilleurs parts dans GNU/linux ...
A lire:
Android Mythbusters (Matt Porter)
Some weeks ago I was attending Embedded Linux Conference Europe. My personal
highlight at this event was the excellent Android Mythbusters presentation
given by Matt Porter.
As you may know, Matt Porter was heavily involved in the MIPS and PPC ports
of Android, so he and his team have seen the lowest levels of Android, more
and deeper than even cellphone manufacturers ever have to look into it.
The slides of his presentation are now available for download. I would
personally recommend this as mandatory reading material for everyone who
has some interest in Android.
The presentation explains in detail why Android is not what most people
refer to when they say Linux. What most people mean when they say Linux is
the GNU/Linux system with it's standard userspace tools, not only the
kernel.
The presentation shows how Google has simply thrown 5-10 years of Linux
userspace evolution into the trashcan and re-implemented it partially for
no reason. Things like hard-coded device lists/permissions in object code
rather than config files, the lack of support for hot-plugging devices
(udev), the lack of kernel headers. A libc that throws away System V IPC
that every unix/Linux software developer takes for granted. The lack of
complete POSIX threads. I could continue this list, but hey, you should
read those slides. now!
Just one more practical example: You cannot even plug a USB drive to an
android system, since /dev/sd* is not an expected device name in their
hardcoded hotplug management.
Executive summary: Android is a screwed, hard-coded, non-portable
abomination.
I can't wait until somebody rips it apart and replaces the system layer with
a standard GNU/Linux distribution with Dalvik and some Android API
simulation layer on top. To me, that seems the only way to thoroughly fix
the problem...
--
--
What's on Shortwave guide: choose an hour, go!
http://whatsonshortwave.tk
700+ Radio Stations on SW http://swstations.tk
300+ languages on SW http://radiolanguages.tk
GIGA LOL pour l'ogre ANDROID, qui devait faire d'une bouchée de la chair à patée de WIndows
HHOOOOHHOHOHO HIHIHIHIHIHHIIIHIIHIIIHI UHUH
c'est pour dire que android n'est pas linux et que google a jete les meilleurs parts dans GNU/linux ...
A lire: Android Mythbusters (Matt Porter)
Some weeks ago I was attending Embedded Linux Conference Europe. My personal highlight at this event was the excellent Android Mythbusters presentation given by Matt Porter.
As you may know, Matt Porter was heavily involved in the MIPS and PPC ports of Android, so he and his team have seen the lowest levels of Android, more and deeper than even cellphone manufacturers ever have to look into it.
The slides of his presentation are now available for download. I would personally recommend this as mandatory reading material for everyone who has some interest in Android.
The presentation explains in detail why Android is not what most people refer to when they say Linux. What most people mean when they say Linux is the GNU/Linux system with it's standard userspace tools, not only the kernel.
The presentation shows how Google has simply thrown 5-10 years of Linux userspace evolution into the trashcan and re-implemented it partially for no reason. Things like hard-coded device lists/permissions in object code rather than config files, the lack of support for hot-plugging devices (udev), the lack of kernel headers. A libc that throws away System V IPC that every unix/Linux software developer takes for granted. The lack of complete POSIX threads. I could continue this list, but hey, you should read those slides. now!
Just one more practical example: You cannot even plug a USB drive to an android system, since /dev/sd* is not an expected device name in their hardcoded hotplug management.
Executive summary: Android is a screwed, hard-coded, non-portable abomination.
I can't wait until somebody rips it apart and replaces the system layer with a standard GNU/Linux distribution with Dalvik and some Android API simulation layer on top. To me, that seems the only way to thoroughly fix the problem...
-- -- What's on Shortwave guide: choose an hour, go! http://whatsonshortwave.tk 700+ Radio Stations on SW http://swstations.tk 300+ languages on SW http://radiolanguages.tk
leeed
Le 05-11-2009, user a écrit :
c'est pour dire que android n'est pas linux et que google a jete les meilleurs parts dans GNU/linux ... [snip l'article très intéressant par ailleurs]
Ton post est très intéressant, mais tu oublies un paramètre fondamental, malheureusement:
P4nd1-P4nd4 ne sait *pas* lire l'anglais.
Le 05-11-2009, user <dag@allemaale.be> a écrit :
c'est pour dire que android n'est pas linux et que google a jete les
meilleurs parts dans GNU/linux ...
[snip l'article très intéressant par ailleurs]
Ton post est très intéressant, mais tu oublies un paramètre fondamental,
malheureusement:
c'est pour dire que android n'est pas linux et que google a jete les meilleurs parts dans GNU/linux ...
Pourquoi les meilleures ?
The presentation explains in detail why Android is not what most people refer to when they say Linux. What most people mean when they say Linux i s the GNU/Linux system with it's standard userspace tools, not only the kernel.
The presentation shows how Google has simply thrown 5-10 years of Linux userspace evolution into the trashcan and re-implemented it partially for no reason.
Ben si il y a une raison : Google voulait juste un noyau pour développer par dessus leur propre système plutôt que de faire une 301ème distribution Gnu/Linux
-- pehache
On 5 nov, 20:15, user <d...@allemaale.be> wrote:
c'est pour dire que android n'est pas linux et que google a jete les
meilleurs parts dans GNU/linux ...
Pourquoi les meilleures ?
The presentation explains in detail why Android is not what most people
refer to when they say Linux. What most people mean when they say Linux i s
the GNU/Linux system with it's standard userspace tools, not only the
kernel.
The presentation shows how Google has simply thrown 5-10 years of Linux
userspace evolution into the trashcan and re-implemented it partially for
no reason.
Ben si il y a une raison : Google voulait juste un noyau pour
développer par dessus leur propre système plutôt que de faire une
301ème distribution Gnu/Linux
c'est pour dire que android n'est pas linux et que google a jete les meilleurs parts dans GNU/linux ...
Pourquoi les meilleures ?
The presentation explains in detail why Android is not what most people refer to when they say Linux. What most people mean when they say Linux i s the GNU/Linux system with it's standard userspace tools, not only the kernel.
The presentation shows how Google has simply thrown 5-10 years of Linux userspace evolution into the trashcan and re-implemented it partially for no reason.
Ben si il y a une raison : Google voulait juste un noyau pour développer par dessus leur propre système plutôt que de faire une 301ème distribution Gnu/Linux
