Yet another take on 64-bits...

64-bit apps have been around for many years now, so it is neither unusual nor unrealistic to expect a major program such as Trados to have entered the realm of 64-bits by the year 2023. Nevertheless, we all should know by now that Trados is a complex program that relies on many other components, resources, and technologies, which probably do not mesh well or at all within a 64-bit environment. I would also assume that most, if not all plug-ins, available in the AppStore would not run with a 64-bit Trados. This was the problem when Microsoft released their first 64-bit version of Office. Microsoft ended up dissuading users from running the 64-bit version! And then, what about Multiterm?

In addition, I get the impression that many users believe that all their performance problems will simply vanish once Trados goes 64-bit. Using Paul’s analogy with car engines, users will probably expect their new cars to immediately drive twice as fast or have twice as much power. I, for one, do not believe this will happen. The best to be expected will be the ability to open larger files. I am skeptical that users will notice an appreciable performance boost. At any rate, I’m not holding my breath on that one.

The fact that Trados still hasn’t cleared the 64-bit bar, speaks volumes for the sheer complexity of the program. This is compounded by the reality of software developers frequently changing jobs and/or assignments. How many of the current developers were around just four years go? How many are currently working on Trados? New developers at RWS must first learn to understand at least part of the code base of Trados before they can be expected to improve or update the product—a time-consuming, daunting task.

Yet another take on 64-bits...

64-bit apps have been around for many years now, so it is neither unusual nor unrealistic to expect a major program such as Trados to have entered the realm of 64-bits by the year 2023. Nevertheless, we all should know by now that Trados is a complex program that relies on many other components, resources, and technologies, which probably do not mesh well or at all within a 64-bit environment. I would also assume that most, if not all plug-ins, available in the AppStore would not run with a 64-bit Trados. This was the problem when Microsoft released their first 64-bit version of Office. Microsoft ended up dissuading users from running the 64-bit version! And then, what about Multiterm?

In addition, I get the impression that many users believe that all their performance problems will simply vanish once Trados goes 64-bit. Using Paul’s analogy with car engines, users will probably expect their new cars to immediately drive twice as fast or have twice as much power. I, for one, do not believe this will happen. The best to be expected will be the ability to open larger files. I am skeptical that users will notice an appreciable performance boost. At any rate, I’m not holding my breath on that one.

The fact that Trados still hasn’t cleared the 64-bit bar, speaks volumes for the sheer complexity of the program. This is compounded by the reality of software developers frequently changing jobs and/or assignments. How many of the current developers were around just four years go? How many are currently working on Trados? New developers at RWS must first learn to understand at least part of the code base of Trados before they can be expected to improve or update the product—a time-consuming, daunting task.

John Mercer 

Hi John,

Good, common-sense reply. I don't have the knowledge to be able to reply thus and am pleased you do!

All the best,

Ali