[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: [Ann] Oxygen XML Editor version 23 release

Subject: Re: [Ann] Oxygen XML Editor version 23 release
From: "B Tommie Usdin btusdin@xxxxxxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 23 Nov 2020 17:32:23 -0000
Re:  [Ann] Oxygen XML Editor version 23 release
> On Nov 23, 2020, at 12:15 PM, Michael Kay mike@xxxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>>
>> I don't see what is unfortunate about people using XSLT 1.0. I don't see
why people dislike the fact that others are using it.
>
> You're building up technical debt. The concept here is that you can spend $N
every year on updating and refreshing the technology you are using, or you can
depreciate your asset by $M per year if you don't, and you need to assess
whether $N exceeds $M.
>
> The depreciation you apply depends on whether you're doing any ongoing
development. If you are, then you should factor in that moving to new
technology will reduce those development costs.
>
> If you want you can also factor in risk (how exposed are you to some major
discontinuity that stops the whole thing working, e.g. a security
vulnerability), support costs (is there anyone who still knows this stuff?),
and staff retention (can you find good people who are prepared to work with
old technology).
>
> So it's not a question of like or dislike, fun or no fun, it's a question of
economics, of minimising the lifetime costs of your system. Of course, the
calculations will come out differently for different projects.

I agree. But it is also a question of timing. The time for an organization to
upgrade should be up to the users, not to the vendors of their tools.

AND, there are things tool vendors can to do make updating easier. For
example, providing guidance on how to "fix" things that "break" in such an
upgrade. If a capability is removed from a product, even if for very good
reason, guidance on how to modify applications that used that capability, are
welcome. Removing capabilities without explicitly providing such guidance
creates anxiety, ill will, and fear.

-- Tommie



======================================================================
B. Tommie Usdin
mailto:btusdin@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.
https://www.mulberrytech.com
17 West Jefferson Street
Phone: 301/315-9631
Suite 207
Direct Line: 301/315-9634
Rockville, MD  20850
Fax: 301/315-8285
-----------------------------------------------------------------------------
---------------------------------------------
Mulberry Technologies: A Consultancy Specializing in XML for Prose Documents
======================================================================

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.