IBM Lotus Notes 8.5 Is The Worst!!!
I just have to say it. I am using Lotus Notes 8.5 in the office, and, to tell you the truth, it's just got to be downright the worst e-mail and collaboration client I have ever been forced to use! It just totally sucks big time!! I hate it, I hate it, I hate it!!!
The first problem I have with IBM's Lotus Notes 8.5 client is the start up time. It's horribly slow! On average, I have to wait 15 full minutes for the resource hog to load. Sometimes, I need to wait another 5 minutes for the application to be in an actually usable state.
I tried optimizing the application by adjusting some Java related configurations. Still, it didn't work well enough to show any appreciable speed. As a last resort, I setup a Local mailbox. The performance is still ugly, seems unstable and, consequently, prone to getting a stupid consistency check process that could take 10 or up to 20 minutes to finish.
In the office, Sametime is integrated into Lotus Notes. Unfortunately, Sametime is just another resource hog to worry about. Even receiving an IM can be a pain. Its copy-paste feature can make the application seem to hang! The IM window may, for some reason, turn all white at times and I would have to save and close the chat in order to see the messages again from the Chat History feature. However, even Chat History is slow to re-load the messages for viewing. Oh, for crying out loud!
In order to avoid the application's lengthy startup time, I don't shutdown the Lotus Notes client anymore. Unfortunately, when you get back the next day, the application becomes much, much slower and would seem to hang at times. Are there memory leaks? I don't know. In the end, you'll have to shutdown Lotus Notes anyway and then opt to re-start your workstation just for good measure.
If the start up time is a problem, so is the application's shutdown time. It takes on average another 10 - 15 minutes to fully unload. Even if the Lotus Notes 8.5 client's window already closed, you can still find the Lotus Notes' process in the Windows Task Manager eating up resources. It would take some time before it would fully disappear. This is terrible since you don't want to interrupt whatever it's doing because you definitely don't want to get that pesky consistency check message again the next time you launch Lotus Notes.
I occasionally experience Lotus Notes 8.5 to crash. At least when it crashes, the application unloads fast and Lotus Notes' process in the Windows Task Manager does not stick around. Crashing is probably the fastest way to unload the application. However, when you try to launch it again, expect another consistency check to waste your time.
IBM should work harder on improving Lotus Notes most especially on performance, performance and performance! There are a lot of UI improvements, true. However, these improvements are no good at all if Lotus Notes 8.5 is very slow to respond. The better looking interface and all the new beautiful features put in are pulled down by the overall experience which is really bad. As it is now, IBM's Lotus Notes 8.5 just got to be the worst application a company could ever be stuck with! It makes you wonder how IBM tests their products...
The first problem I have with IBM's Lotus Notes 8.5 client is the start up time. It's horribly slow! On average, I have to wait 15 full minutes for the resource hog to load. Sometimes, I need to wait another 5 minutes for the application to be in an actually usable state.
I tried optimizing the application by adjusting some Java related configurations. Still, it didn't work well enough to show any appreciable speed. As a last resort, I setup a Local mailbox. The performance is still ugly, seems unstable and, consequently, prone to getting a stupid consistency check process that could take 10 or up to 20 minutes to finish.
In the office, Sametime is integrated into Lotus Notes. Unfortunately, Sametime is just another resource hog to worry about. Even receiving an IM can be a pain. Its copy-paste feature can make the application seem to hang! The IM window may, for some reason, turn all white at times and I would have to save and close the chat in order to see the messages again from the Chat History feature. However, even Chat History is slow to re-load the messages for viewing. Oh, for crying out loud!
In order to avoid the application's lengthy startup time, I don't shutdown the Lotus Notes client anymore. Unfortunately, when you get back the next day, the application becomes much, much slower and would seem to hang at times. Are there memory leaks? I don't know. In the end, you'll have to shutdown Lotus Notes anyway and then opt to re-start your workstation just for good measure.
If the start up time is a problem, so is the application's shutdown time. It takes on average another 10 - 15 minutes to fully unload. Even if the Lotus Notes 8.5 client's window already closed, you can still find the Lotus Notes' process in the Windows Task Manager eating up resources. It would take some time before it would fully disappear. This is terrible since you don't want to interrupt whatever it's doing because you definitely don't want to get that pesky consistency check message again the next time you launch Lotus Notes.
I occasionally experience Lotus Notes 8.5 to crash. At least when it crashes, the application unloads fast and Lotus Notes' process in the Windows Task Manager does not stick around. Crashing is probably the fastest way to unload the application. However, when you try to launch it again, expect another consistency check to waste your time.
IBM should work harder on improving Lotus Notes most especially on performance, performance and performance! There are a lot of UI improvements, true. However, these improvements are no good at all if Lotus Notes 8.5 is very slow to respond. The better looking interface and all the new beautiful features put in are pulled down by the overall experience which is really bad. As it is now, IBM's Lotus Notes 8.5 just got to be the worst application a company could ever be stuck with! It makes you wonder how IBM tests their products...
Comments
Post a Comment