🚀 go-pugleaf

<In my eyes, FrameMaker 7 is not mainframe. It's mainstream because it exemplifies a tool straddling many modern processes. Work smarter.> 

Some very good points, but what I think (as the author points out) still keeps Frame in the mainframe niche market, is that aside from providing stability and a full publishing solution, Adobe has done nothing to improve the usability since adopting it from Frame, Inc, thus keeping as a mainframe solution that others refuse to adopt. 

Adobe has a very powerful application that has capablities beyond any other DTP (though Ventura is making ground) tool out there. And (as the author points out) Adobe has identified XML as the future of publishing and dedicated an entire Frame release (version 7) to encompass that support alone. Now they possess the only current tool that offers a full XML/structured publishing solution that is built on top of technology with a 1985, UNIX, look and feel. 

How can you appeal to new markets and convince them that you are delivering a cutting edge publishing solution (currently the first of its kind), when the software still ships with an unattrative (for lack of a better word) interface, a high learning curve, zero customization options, lack of standard DTP features, and the same high price tag?