Re: [IBMiOSS] gmake: *** virtual memory exhausted. Stop.

I think you're both right. There are different roles in open source.
It's true you don't need to know C for many things, but you will most
likely need to compile C (native extensions of Node.js, Python, Ruby, PHP,
etc) once you get deeper into projects. These don't require you learn C
but it does require that you understand compile errors (i.e. include not
found, gcc not found, etc). Let me further qualify that last statement by
saying many times things are compiled for you under the covers (so near
zero C knowledge required, but C is still involved/compiled).

A lot of the current issues floating through this channel have to do with
having an environment setup correctly. We will eventually have a good
recipe and will subsequently/continuously document it in ibmichroot
configurations** (they're like Docker configurations). It's worth noting
other platforms have many of the same exact issues and they are resolved
through automation and patterns (why Docker is such a boon to productivity).

**here's a minimalist config: bit.ly/ibmichroot-chroot_minimal

Aaron Bartell
litmis.com - Services for open source on IBM i


On Wed, Jul 13, 2016 at 4:35 PM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Wed, Jul 13, 2016 at 3:10 PM, Aaron Bartell <aaronbartell@xxxxxxxxx>
wrote:

The following is from Tony Cairns (IBM, PASE/and-more expert)....

Open Source projects require many tools beyond gcc compiler. Open Source
projects requires c coding knowledge. Open Source projects require domain
specific knowledge. All in all, simply impossible to describe on this

wiki

page all aspects need to learn to develop successful Open Source

projects.

In fact, most likely that only experienced c coders and/ or Open Source
developers will use the actual gcc environment.

I fully respect and acknowledge Tony's position here. It reeks of
knowledge and experience.

However, I would submit that a large part of why OSS is flourishing
now is that, given a proper, fully functioning Python, Ruby, or
Node.js environment (just to name a few), you can build quite
impressive and useful stuff *without* having to drop down to C or
other system-level programming. And even Java, which is often
ridiculed by Python/Ruby/Perl/etc. users as oppressively verbose and
overly bureaucratic, is still a ton easier to just get stuff working
in than pure C, and fully functioning JVMs are practically everywhere.

So, I get the thrust of what Tony is saying, but I also want to
reassure open source newbies that you don't HAVE to know C to
participate fruitfully in open source.

At risk of insulting knowledgeable developers, here is the truth most of

us

learn about developing Open Source.

I'm not insulted, but maybe that just means I'm not knowledgeable enough.
8)

John Y.