Unix or Windows for your Automated Catalog?

This was recently sent to the Web4Lib E-Mail list service:

Dear Colleagues,

Our library is in the process of selecting a new automated system. We are a medium-sized library with 30 service points, one of which is a large central library. Our current platform is off the table as an issue, as is any expertise I bring to the discussion after twenty odd years of automating libraries. Since I’ve been told that I — as a mere librarian — do not have the requisite perspective to make such a decision, I was wondering if you all would be willing to help me out?

What are the pluses, and minuses, of each platform? Thanks for your assistance.

This was recently sent to the Web4Lib E-Mail list service:

Dear Colleagues,

Our library is in the process of selecting a new automated system. We are a medium-sized library with 30 service points, one of which is a large central library. Our current platform is off the table as an issue, as is any expertise I bring to the discussion after twenty odd years of automating libraries. Since I’ve been told that I — as a mere librarian — do not have the requisite perspective to make such a decision, I was wondering if you all would be willing to help me out?

What are the pluses, and minuses, of each platform? Thanks for your assistance.

I thought this to be an interesting question that warranted some discussion here.

Windows has the disadvantage of requiring so many service packs, and of course needing the reboot after. As for Unix, I found that vendors don’t upkeep the Operating System for you, so unless there is someone on staff who is not afraid to get their hands dirty, you might wind up with a system that can be easily compromised. What do other LISNews users say?