Furthermore, I get that IBM does not want to support software they no longer
own and maybe even not have the ability to support. So freeze the data in
that portion of developerworks and make it read only. Give us 24 months to
migrate the data to another technology, IBM's or elsewhere. When balanced
against the probable loss of revenue in support agreements from customers
that only needed that one last push, let alone upgrades, it would be cheap
to keep the systems in place for 2 years.
Only another in a long line of massive blunders in acquisitions/sell offs.
Lets see: OS/2 is more or less killed by a separation contract with
Microsoft that gives them the underlying code and allows NT to come out
instead of stopping Microsoft at 3.11. Sun purchase is messed up because
someone did not want to give the Sun executives the bonus they wanted,
(Ellison so no problem with it....), now HCL. I've got customers that 120
days ago would have tossed Microsoft to the curb in a heartbeat if they
suggested Outlook to them, now they are inviting Microsoft in. Think
Microsoft is going to stop at email? On the good news side, RedHat,
Rational, and a couple of others.
Agile Technology Architects
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Sent: Friday, November 1, 2019 10:48 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: DeveloperWorks Shutdown
And that's pretty much spot on with what Ranga and I are telling them.
I have also been observing the URLs as I get data and yeah it's WAY up
there. What's worse is their insentience that 'The Community' will just deal
with it by migrating their content to the new community or perhaps somewhere
I've been told by some who've tried that the new communities have different
page rules and requirements so it's not a simple re-post, it's a full rework
to get the content in there.
Further IBM ignore with that is often the content is created by people in
spare time, not paid, and as a consequence they simply don't have the
bandwidth to make that move. For some it will be 'the last straw' and the
content, it not preserved in another way, will vanish.
And even IF it moves will you be able to find it???
- Larry "DrFranken" Bolhuis
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 11/1/2019 10:56 AM, midrangel@xxxxxxxxxxxxxxxxx wrote:
In ITJungle the IBM director with responsibility to Developerworks,
Greg Gorman says we "overreacted to the announcement and that the
closures are not a broad as they are believed"
That may be a true statement. I will counter with being alarmed at:
"We are removing half the brain of the patient" as being just as
overreactive since the brain is only a small percentage of the total
body weight of the person.
Since that announcement I have tracked every time I use information
from that portion of Developerworks that is "being sunsetted" and it's
nearly 98% of the time. Mr. Gorman is clearly not informed of the
criticality of the information contained in that portion of the site,
and clearly does not care. IBM documentation is good. Everything is
in there. It's also almost useless when really figuring out how to do
things. Hence the Developerworks Wiki portion has become IBMs way of
making things easy. Mr. Gorman apparently does not know or care about
this fundamental truth.
Put another way: How to hack off your most ardent supporters and get
their management to start looking for alternatives.
Nice play IBM.
Agile Technology Architects
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
As an Amazon Associate we earn from qualifying purchases.