🚀 go-pugleaf

Mark Borgerson <mborgerson@comcast.net> wrote:

>In article <dafol711s6vn5v2ilqir5fep0j2acf8q2d@4ax.com>, 
>joseph_barrett@sbcglobal.net says...
>> 
>> On Sun, 11 Mar 2012 10:42:25 +1100, Chris Baird
>> <abuse@brushtail.apana.org.au> wrote:
>> 
>> >>> 64MB! (and promises it running Android!)
>> >>> 
>> >>> Even a programming language like Haskell, run from the command line,
>> >>> needs more core than that. C++ programs can easy need 200MB+ of real
>> >>> RAM to compile.
>> >
>> > > Um, not. That is the GUI/DE that eats all that RAM. The actual
>> > > functionality is maybe 5 to 10 % of that.
>> >
>> >Are you using the Hollywood edition of C++ with Gibson extensions
>> >enabled? (Usually installed under the name 'Java'.)
>> >
>> >Memory usage while compiling KDE4 C++ sources from the command line:
>> >
>> >  PID USERNAME PRI NICE   SIZE   RES STATE      TIME   WCPU    CPU COMMAND
>> > 1333 root      25    0   332M  316M CPU/0      0:17 96.03% 57.03% cc1plus
>> > 1351 root      85    0    48M   32M pager_/4   0:00  2.47%  1.46% as
>> >
>> >316MB in use by the compiler. C++ is Peeeg. And then there's Java, which
>> >is Mrs Peeeeg after 8 years of marriage..
>> >
>> >And it was said this proposed supercheap 64MB RAM RaspberryPi killer
>> >would run Android and its Java systems. Uh, you need at least 768MB of
>> >RAM for Android to be usable at all.
>> 
>> The toolchain were not on the RPi. It was just the target.  Just the same
>> your point has been made, those toolchains take gigs.
>> 
>> ?-)
>So to do any programming of the RPi,  you still need a PC with Linux 
>either native or in a virtual machine.  Of course the same is true of
>any other low-cost system.
>
>It does seem disingenuous to promote the idea that you could do 
>significant hardware and  C software development with the RPi and just
>a keyboard, monitor and mouse.  You really need a PC and a second
>keyboard, monitor and mouse unless you plan to switch a lot of cables
>when you want to test your software.

That would be faster but you don't need an extra keyboard and monitor.
You can work remote from a Linux system. Mount the filesystem of the
RP using fuse and have the RP use the Linux system as X server for
output.

-- 
Failure does not prove something is impossible, failure simply
indicates you are not using the right tools...
nico@nctdevpuntnl (punt=.)
--------------------------------------------------------------