× 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.




On 2014-08-07, at 2:12 PM, Gqcy <gmufasa01@xxxxxxxxx> wrote:

we do now own seats of RDi...
how did others answer these questions:

1) why should we reward IBM when they used a bait-and-switch to get us
to buy the tools (WDSC,code/400 was "free")

They didn't - they just changed the packaging. Did you complain when they _added_ Code/400 (and subsequently WDSC) to the toolset without charging you? They completely repriced and repackaged all the compilers and tools at V6.

Don't get me wrong, I'd much rather not have to pay - and my copy literally is paid for out of my own pocket.


2) why should we pay for IBM's IDE, for you old RPG green-screen programmers... our PHP, js, html programmers just love their free
IDE's?

Zend charge for Zend Studio, others charge for sophisticated Java IDEs. There is a free RPG IDE (RPG NextGen) if you don't want to pay - but just as NetBeans PHP can't do all that Zend Studio does NextGen can't hold a candle to RDi. A few free IDEs are as good as the for-fee ones, but those tools typically evolve in areas where there are huge numbers of developers. The size of the market for RPG IDEs is much smaller and the pricing reflects that.


On 8/7/2014 1:01 PM, Buck Calabro wrote:
On 8/7/2014 1:06 PM, Jon Paris wrote:
I think you can make the argument Buck that given the filtering and outline capabilities that someone who is only doing investigate work could benefit even more from RDi than a developer.

The more I respond to this thread, the more I think I'm not the right
person anyone should listen to. I wasn't pushed to RDi by management,
persuaded by marketing, jeered by colleagues or lured by magazine
articles written by industry leaders.

I'd used other editors (TECO and Emacs at least) before I used SEU and I
always thought SEU was... thin. I always wanted something better. My
first go was with Brief, and I spent quite some time at home writing
extensions I could syntax check with, etc. When we had to get an OS/2
machine for a specific business app, I was able to get a copy of
Code/400 and immediately fell in love with it - especially Rexx macros
and regular expressions. Two more reasons I think I'm the wrong person
for this thread.

When I see a company spend many hundreds of thousands on software
packages and then state that $4k is too much to spend on the software
support people, it's almost always because the software group isn't
interested in what that $4k is for. Additionally, I've personally seen
a form of premature optimisation at work - the developers themselves
look at the price tag and think that management wouldn't spring for it.
And they themselves decide not to make the request of management.

It just seems like a chicken and egg problem to me. Until midrange
programmers are exposed to other editors, they just don't realise what
they're missing. And because they're at the stage where good enough
seems to be working, there's no demand for anything better.
--buck

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.