I would agree that, unless I hear otherwise, I would expect ACL to still be
around in the next 3-5 years.
Where I differ from many of my other developer-types (other than not having
the BS in CS, you weren't the only one that had to do it the hard way,
Lynn), is that I would hate to see ACL go away. Others can complain that
"it's not an open language" and "it's a proprietary solution", but it's a
good tool for getting a lot done quickly. Plus, it's so tied into the
infrastructure of Epic that trying to replicate some of the functionality
that ACL provides would be time-consuming at best, and infuriating at worst.
It's just a good-enough blend of Perl and C to be useful, plus the help
documentation (IMO) is an impressive example of how scripting languages
SHOULD be documented.
Honestly, if Arbortext wanted to phase out ACL, what I would LOVE to see
(and I can't say how hard this would be), is for them to implement the
majority of ACL functionality with another, open scripting language. If
they could replicate most of the ACL funcs and commands with, say, Python
(or preferably Jython), can you imagine how much more you could do within
Don't get me wrong, I don't hate Java, it's good for it's intended purpose.
It's just there's so much in ACL that can be performed with one alias or
func that takes on so much extra complexity trying to recreate in Java.
Just my 0.02-
-Jason A. Buss