× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Now tell me that node.js is that easy? Or Python?

We're not comparing apples to apples. Node.js and Python, as languages,
~are~ as easy (actually easier) than PHP to install. It's when we get into
native language extensions that we get into discussions like this. PHP has
the same issue(s). It's not as noticeable with PHP because Zend has taken
the time to port some of the more popular native stuff.

Going back to one of my earlier comments, there will be many roles in this
open source world on IBM i. Some will figure out these "virtual memory
exhausted" errors and others will focus on less complicated things. The
deeper you desire your role to be the more time that must be spent learning.

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


On Fri, Jul 15, 2016 at 4:48 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

The “E” word.

Education. Or at least provide some bridge documentation. Thought I’d
made that clear but apparently not.

Without that you basically limit your audience to those who already
(perhaps through a past life or hobbyist stuff) understand this stuff and
those (relatively few) who are prepared to struggle through and try and
learn. And that will be a pathetically small percentage of the potential
users.

PHP has succeeded in part because these many of these issues were
addressed. Install via a familiar process, package install via the Zend
console. Sure you occasionally have to dive down to get some things done
but by the time you need that you have a fully functioning system up and
running.

Now tell me that node.js is that easy? Or Python?

I REALLY want this OS stuff to work - PHP has given us a massive boost -
but it needs work.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 15, 2016, at 5:39 PM, Kevin Adler <kadler@xxxxxxxxxx> wrote:

"OpenSource" <opensource-bounces@xxxxxxxxxxxx> wrote on 07/15/2016
03:43:01 PM:

From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Date: 07/15/2016 03:43 PM
Subject: Re: [IBMiOSS] gmake: *** virtual memory exhausted. Stop.
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxx>

<snip>
The point I’m trying to make is that you can’t explain jargon with
more jargon. It has to be stated in the terms your target user is
already familiar with. If learning all this stuff was easy for us
old farts a lot more people would be grepping all over the place in
the IFS and making far more use of PASE. The fact that so little use
is made of what we already had _before_ this OSS stuff came along
should have been a hint to IBM.

So what are you proposing IBM should do? Make all this new open source
stuff fit in to GO LICPGM? Or do you just need a Rosetta Stone of sorts?

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.