Adobe Kills FrameMaker for Mac
Feneric writes "As noted on FrameUsers.com, FrameMaker for the Mac was officially killed by Adobe. Of course, since one of the primary selling points of FrameMaker is its wonderfully solid cross-platform MS-Windows / Macintosh / Unix support, many are now wondering how long it'll now last for any platform."
"[...] many are now wondering how long it'll now last for any platform."
I think the real question is "how long it'll last for any platform other than Windows?"
Sad.
Trolling is a art,
Truly cross-platform, professional page layout, incredibly smart fonts and free! Stop chaining yourself to proprietary shit that can get killed any day.
As cool as it is too see major software being released for multiple platforms, especially linux. Something like this is going to happen. Just a few weeks ago, Macromedia announced that it was going to support linux. Now adboe is dropping a mac product.
Adobe never actually updated FrameMaker for OS x on the Mac, which made this a legacy app that needed to run in Classic anyway. Print shops can be somewhat slow in updating to newer software and technology, so many might still run some OS 9 Macs...but lack of support for the current system hinted that this software was considered dead long ago.
-Barkeep, a draft of your most hazardous brew, for the world is slowly stepping into focus, and I don't like what I see.
...that Adobe has puchased a competitor and then killed off the competing product. Didn't they do the same thing with PageMaker?
In any case, it would seem difficult for a company to justify splitting its development resources between two competing products. FrameMaker users surely must have (or should have) seen this coming.
Adobe is a company that needs to make money to survive (like all companies). If a product isn't selling well enought, it will get killed.
So the fault isn't squarely on Adobes shoulders in this - the particular segment of the market that Framemaker for Mac catered to just isn't big enought for the software to keep selling...
On the lighter side, this must be a wonderfull opertunity for the Open Source Software to show that it can deliver somethign just as good for the Mac, right?
Everything in the world is controlled by a small, evil group to which, unfortunately, no one you know belongs.
A bigger question for Framemaker user currently on Mac is do they qualify for the next upgrade version, transitioning from Mac to Windows?
Macromedia has done a great thing in packaging MX2004 with both Mac and Windows versions in the same box -- I can upgrade any of my systems -- mac, or windows -- and use the software on the fastest box in my studio.
Software makers have been telling us for decades that hardware is a commodity and software is what's important. It's about time that the liscensing model changes to reflect that.
This is a great chance for Adobe to do just that. I hope they do.
First you don't update FrameMaker for the Mac in two years, then you complain Mac sales are going down and now you kill it. Uh, if you updated it more often maybe people would buy it.
CDE open sourced! https://sourceforge.net/projects/cdesktopenv/
FrameMaker still beats any other word processor-like application for large document production. I'm part of an engineering organization and we've looked at moving from FrameMaker but nothing else replaces it without the loss of a lot of functionality. A bunch of people could colaborate on a document, pull it together and publish it. We're engineers, not typesetters so while InDesign could do it (I'm sure anyway) we're not about to learn a new package just for this purpose.
We've played with OpenOffice templates but there doesn't seem to be a real way to handle pulling together a document. TeX can do it but it would have a steep learning curve for something that isn't our primary purpose. I know TeX myself but I'm not about to be the one who gets tapped to teach it to everybody else (all the while still working hard at doing solid engineering work)
FrameMaker was painful in some ways, mostly because it wasn't "Just a word processor". Once that aspect was realized it was fairly painless however.
Chris Kuivenhoven is a thief, beware
Windows or Solaris only.
If it runs on Solaris, why not a Linux version? They're practically the same thing!
ok, I know, it was bad, but it had to be said.
-PainKilleR-[CE]
From the Adobe Framemaker FAQ on the article "A. It is our policy to not comment on the size of our user base. However, sales of FrameMaker licenses have been greater on the Windows and Solaris platforms for a number of years." They spelled it out and no tinfoil hat conspiracy.
You may never see Framemaker on an open source platform. The primary use for Framemaker is technical documentation for publication. Some of the deadtreeware available for open source project certainly was composed in Framemaker. However, the majority of open source projects are not at the stage (and may never be) where someone makes the effort to publish documentation.
And then remember a large number of Framemaker users work as software technical writers for closed source software companies. So do not hold your breath for the free software version.
Framemaker is one of the few pieces of software, open or closed source, that paid more than lip service to XML. A structured Framemaker document is a pure XML document with a real DTD. So not only is it well formed, but also (*gasp of disbelief*) Valid!
Have you Meta Moderated t
How many PhD student want to spend the money on Word when they can use LaTeX for free? And don't say they can write their dissertation in a lab, you can't even bring coffee in there. Plus, Word's equation editor is an atrocity against man.
I haven't heard anyone say they are using Framemaker for serious development of anything in years.
That's because FM is not a general-purpose Joe-and-Jane office worker word processor: FM's strengths lie in really large documents, like books and other things that are over ~200 pages. Not many people have a need for that. FM on Solaris (SPARC) is a very nifty combination.
You and your acquaintances are not a statistically significant sample set.
I want to drag this out as long as possible. Bring me my protractor.
What about other critical features being able to place figures and text-frames exactly where you want them (and not where LaTeX wants to misplace them)
There are rules for typesetting documents. TeX (and by extension, LaTeX) uses those rules. Word is like a plastic hammer and toolbelt for children compared to TeX's professional Estwing.
tracking changes/version control?
This is not the job of a word processor.
Think back to two years ago: do you think perhaps Adobe was swamped with DMCA-related questions?
Where exactly did you send your query? To a person or to a {help|info|webmaster|etc}@adobe address?
Was your question a FAQ? Did you bother to check?
To recap:
you sent email to a huge company
you didn't get a reply
feeling slighted, you sent a "less polite" email threatening to "boycott their products"
for some amazing reason, you didn't get a response to the second email
you took all this personally, and now are waging jihad against a company that doesn't know/care about your [alleged] lost business
Wow.
I want to drag this out as long as possible. Bring me my protractor.
Frame is the tech writing industry standard for anything bigger than what Word can handle. If you're going for any tech writing work of consequence, you'd better be handy with Frame.
Unfortunately, tech writers seem to march to the Microsoft drummer in general. I doubt many will care about Frame for OSX.
Ahh how refreshing to hear a state/government employee voting with someone elses (taxpayers) wallet.
That deal for the products did cost money, just not money out of *your* pocket.
Check your knees - they seem to be jerking a lot. Adobe didn't stop you from using this. You can use the product for as long as you want, there will just not be any updates. You could put this on an OS9 machine and use it for years. Just saying that there will be no upgrades, does not mean they stop you from using it. Save your closed source arguments till they are justified.
Stay tuned for new sig...
Apparently said person has never actually had any experience with porting software in their lives?
I've always used PageMaker, Illustrator and Photoshop.
Photoshop, oddly enough, was not originally designed with the print industry in mind until John and Thomas Knoll from Lucasfilm's Industrial Light and Magic had sold it to Adobe.
Adobe's definitely feeling a kick in the pants from Apple...
Apple's developers, being far more ingenious at developing intuitive and user-friendly interfaces, has vastly improved acquired applications such as Shake and DVD Studio Pro.
As a result of an explosion in digital cinematography and editing, people with advanced programming skills are harder to find, and therefore there's a greater need for user-friendly, robust apps on the superlative media platform.
Adobe has been riding high on Photoshop for years, and I find that particularly interesting since neither was Photoshop their product (it was invented by Thomas and John Knoll, of Lucasfilm's Industrial Light & Magic), nor was it ever marketed by Adobe for the purpose for which it was invented... digital matte artistry and frame-by-frame image correction in motion pictures.
Unfortunately, they haven't really delivered on other products...Newer versions of Premiere had odd compatibility problems with various DV cameras, various interface bugs, a very poor titling tool that crashes frequently... Premiere Pro seems a desperate attempt to recover market share lost to Apple's vastly superior Final Cut Pro, imitating almost every major feature set of Final Cut Pro that was conspicuously absent in the standard version of Premiere.
As for After Effects... That application's edge was trumped when Apple acquired Shake, which has been used in Oscar-winning productions for seven straight years, including [i]Lord of the Rings[/i]... Shake is such an immensely powerful compositing system, it commands a sticker price four times that of After Effects Production Bundle. It's clear that Adobe's reign in the film and television industry is at its end... which means "Game Over" for one of their two primary target markets. So my response, as a content creator using Macs exclusively, to this and future missteps by Adobe in an effort to differentiate themselves from Apple who has all but entirely annihilated Adobe's market share... is, to quote Bender from The Breakfast Club, "B-O-O H-O-O."
Cry me a river...
If Apple ever plans to massively overhaul MacPaint and turns AppleWorks into a full-blown publishing suite, Adobe might as well file Chapter 11.
Mac users are very parochial about the UI. I don't mind using X to run useful apps like Unison, but most would.
FYI: Any magazine or catalog you open will be produced either in Quark (most of them) or InDesign (a few). Framemaker has a very small, very select market, for which it is a superior product. For anything else it's a pain in the ass.
I am a believer of momentum and curves.
Not at all; the difficulty is not in the POSIX bits - read/write/open/close - but in the GUI. A well behaved Mac app needs to use unique Apple API's correctly, such as Cocoa. Besides, support can be a bigger issue than initial porting. I know of products that could be ported to Linux in a heartbeat, except that the support issues scare the owners.
Anyhow, Frame is essentially a corporate product and corporations have not accepted the Mac to any great extent. It's used in graphic arts, prepress, etc. but most IT departments would rather avoid them. The Mac mostly sells to consumers and independent professionals.
FrameMaker is the ONLY Mac option for long-document work. Period. Adobe is forcing the hand of those of us who are Mac-based tech writers -- either we go on using FM in Classic mode until that doesn't work any more, or we get a PC for our FM projects. Can't say I didn't see it coming when they ignored OS X, but it hurts anyway.
Mac users are very parochial about the UI. I don't mind using X to run useful apps like Unison, but most would.
Exactly. I had that experience today firing up The GIMP 2 under OS X today for the first time. It's the first time that I've fired up any X app other than an x-term (never had any need to) and the dichotomy between the two UI's made me want to puke.
So, I quit GIMP, fired up Photoshop and give it a big electronic hug.