[Info-vax] HP Integrity rx2800 i4 (2.53GHz/32.0MB) :: PAKs won't load

Stephen Hoffman seaohveh at hoffmanlabs.invalid
Mon Feb 29 10:21:03 EST 2016


On 2016-02-29 06:25:04 +0000, lists at openmailbox.org said:

> Hoffman may be the world's biggest pessimist and insider VMS-basher but 
> he sure has a way with words!

Were I bashing, there would not be specific suggestions referenced.    
Maybe reconsider how forward progress is made with products and 
projects — sycophancy and statements of membership and of allegiance 
just aren't going to produce meaningful enhancements.   If problems and 
limits aren't identified, then they aren't resolved.    This any more 
than an unwavering commitment to upward-compatibility can be congruent 
with resolutions and remediations for the more intractable idiocy with 
OpenVMS.  If flagrant and utter stupidity is not identified and 
deprecated — application configuration settings via logical names, or 
the cluster common file morass, etc — then it only breeds and 
multiplies.  More complexity.   More chaos.  More confusion.

As for the "world's biggest pessimist" about OpenVMS, consider that HPE 
remains committed to the delivery of the roadmap for the retirement of 
HPE OpenVMS.    Consider too the *many* folks that have already ported 
off of OpenVMS, and ports presently underway.    The staff at VSI are 
all phenomenally talented, and I have great respect for the entire 
team.    Whether the staff can get enough work done and quickly enough 
— and within their minuscule and colossally constrained budget — to 
convince enough existing OpenVMS folks to stay and particularly to 
convince enough new vendors and enough new applications to deploy on 
OpenVMS?  VSI has to make money, and in a market that's supremely 
competitive and a market with far larger and better-funded competitors 
quite literally giving away their products, and — until and unless the 
VSI folks can bend the trend — the OpenVMS customer base is static at 
best and declining over the longer term.

VSI is already curing existing messes that my OpenVMS customers have, 
such as with their Apache 2.4 port.   Now whether they can artfully 
remediate the inevitable messes in ~forty years of legacy OS code, and 
sufficient to keep the current customer base happy and to make the 
product interesting to new users and new deployments?



-- 
Pure Personal Opinion | HoffmanLabs LLC 




More information about the Info-vax mailing list