Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.forth > #52892 > unrolled thread

please forthers work together and get rid of java

Started bypolymorph self <jackvanc3@gmail.com>
First post2016-11-27 00:38 -0800
Last post2016-12-01 00:27 -0800
Articles 3 — 2 participants

Back to article view | Back to comp.lang.forth


Contents

  please forthers work together and get rid of java polymorph self <jackvanc3@gmail.com> - 2016-11-27 00:38 -0800
    Re: please forthers work together and get rid of java Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2016-11-27 05:13 -0500
      Re: please forthers work together and get rid of java polymorph self <jackvanc3@gmail.com> - 2016-12-01 00:27 -0800

#52892 — please forthers work together and get rid of java

Frompolymorph self <jackvanc3@gmail.com>
Date2016-11-27 00:38 -0800
Subjectplease forthers work together and get rid of java
Message-ID<ef888744-41de-44bd-b21a-b83093f91aa6@googlegroups.com>
please!

[toc] | [next] | [standalone]


#52896

FromRod Pemberton <NeedNotReplyHere@xrsevnneqk.cem>
Date2016-11-27 05:13 -0500
Message-ID<20161127051302.672d872c@_>
In reply to#52892
On Sun, 27 Nov 2016 00:38:35 -0800 (PST)
polymorph self <jackvanc3@gmail.com> wrote:

> please!

Why?


Reliable software takes many thousands of man-hours to develop and
debug.

I.e., once everyone is on the same sinking ship, no one is going to
jump ship to another sinking ship, which will likely sink even faster
than the sinking ship they're currently on.  Of course, in your case,
the other sinking ship has yet to be built.  There is nothing to jump
onto.

What I'm trying to say is that everyone who uses Java has a vested
interested in continuing to use Java.  They've trained many employees
to code using it.  They've hired many employees whom program it.
They've developed more and more code using it.  They've determined how
to manage code development and coding mistakes when using it.  They've
licensed code and libraries coded for it.  It's a large investment.
They'll lose whatever monies they've invested if they replace it.

Therefore, your manager is not going to switch from Forth, C, PL/I,
COBOL, Fortran, or whatever to Java, because he has a vested interest in
preserving his overpaid job.  He doesn't care about what's in your best
interest or even the company's best interest.  He wants to continue to
be overpaid, manage only a few employees or hire an occasional
consultant or two, drink lots of free company coffee, spend most of the
day talking with other employees about sports, take two hour lunches
with alcohol, spend only 15 minutes per day actually working, and
finish the day playing basketball using the company facilities.  He
doesn't care that if your company's code base was ported to C, that
it'd be worth hundreds of millions of dollars, if you licensed to your
competitors.  He doesn't care about opportunity or advancement
anymore.  He cared about that 10 or 20 years ago when he was younger,
hungry, and full of potential.  But, climbing the corporate ladder
killed that.  Now, he's over-promoted and overpaid.  Except for his
alcoholism, divorce, child support payments, and dual house payments,
he's happy. He only cares about not losing his exceptionally easy, good
paying job in a rough economy.  So, from your manager's perspective,
porting your code base to another language only introduces coding bugs,
financial risks, and a political backlash that could get him fired.


Rod Pemberton

[toc] | [prev] | [next] | [standalone]


#53010

Frompolymorph self <jackvanc3@gmail.com>
Date2016-12-01 00:27 -0800
Message-ID<c5681dc4-2ba9-4b1b-a904-a4a9d6b003aa@googlegroups.com>
In reply to#52896
On Sunday, November 27, 2016 at 5:12:29 AM UTC-5, Rod Pemberton wrote:
> On Sun, 27 Nov 2016 00:38:35 -0800 (PST)
> polymorph self <jackvanc3@gmail.com> wrote:
> 
> > please!
> 
> Why?
> 
> 
> Reliable software takes many thousands of man-hours to develop and
> debug.
> 
> I.e., once everyone is on the same sinking ship, no one is going to
> jump ship to another sinking ship, which will likely sink even faster
> than the sinking ship they're currently on.  Of course, in your case,
> the other sinking ship has yet to be built.  There is nothing to jump
> onto.
> 
> What I'm trying to say is that everyone who uses Java has a vested
> interested in continuing to use Java.  They've trained many employees
> to code using it.  They've hired many employees whom program it.
> They've developed more and more code using it.  They've determined how
> to manage code development and coding mistakes when using it.  They've
> licensed code and libraries coded for it.  It's a large investment.
> They'll lose whatever monies they've invested if they replace it.
> 
> Therefore, your manager is not going to switch from Forth, C, PL/I,
> COBOL, Fortran, or whatever to Java, because he has a vested interest in
> preserving his overpaid job.  He doesn't care about what's in your best
> interest or even the company's best interest.  He wants to continue to
> be overpaid, manage only a few employees or hire an occasional
> consultant or two, drink lots of free company coffee, spend most of the
> day talking with other employees about sports, take two hour lunches
> with alcohol, spend only 15 minutes per day actually working, and
> finish the day playing basketball using the company facilities.  He
> doesn't care that if your company's code base was ported to C, that
> it'd be worth hundreds of millions of dollars, if you licensed to your
> competitors.  He doesn't care about opportunity or advancement
> anymore.  He cared about that 10 or 20 years ago when he was younger,
> hungry, and full of potential.  But, climbing the corporate ladder
> killed that.  Now, he's over-promoted and overpaid.  Except for his
> alcoholism, divorce, child support payments, and dual house payments,
> he's happy. He only cares about not losing his exceptionally easy, good
> paying job in a rough economy.  So, from your manager's perspective,
> porting your code base to another language only introduces coding bugs,
> financial risks, and a political backlash that could get him fired.
> 
> 
> Rod Pemberton

brutal

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.forth


csiph-web