Slashdot Mirror
IBM Buys Rational Software
An anonymous reader writes "Rational Software is going to be taken over by IBM. More info on Rational's website. RIP Rational. This is what rational is sending it's customers:
To our valued customers:
We are delighted to tell you that IBM and Rational Software have announced a definitive agreement for IBM to purchase Rational. This is a very exciting time for both companies and builds on the extensive business relationship IBM and Rational have had for over 20 years. Most importantly, it will provide significant benefits to you." Other readers submit links to the story in InformationWeek and the Mercury News.
What is this some type of cult now?
Instead of coming up with weird 'royalty' reasons, come up with good business reasons for IBM to open source this product.
Hey, I'd love if they do that, and you could argue that there could be some benefits financially to IBM. However, from IBM's perspective, I don't see this is a great move, or something you do right off you buy a company.
- sigs are for wimps.
Rational software is some of the worst designed examples of user interface out there. There are two types of people that like rational software:
1. They haven't used anything better like togethersoft or visio.
2. They are management and don't actually have to use it.
Rational and IBM should get along great. Neither company produces good software. But both companies produce incredible salespeople. Working for a large bank, I have a great deal of respect for these guys. How would you like to try selling IBM or rational products? As engineers we are usually too honest. I'd never get anywhere.
Rational sells a process. The process is great for business people because it produces visible artifacts. (Aptly named, as they don't get used and are only good in the archeological sense.)
Togethersoft (recently bought by Borland) has much better software but it is very expensive, and they don't have the quality salesforce IBM has.
So if you think that salespeople don't matter, think again. In this case, they can take a barely functional product and have it dominate that sector of industry. Even in the face of better products.
I have used clearcase under two environments:
1) My last job: an all-unix network, where all the vobservers and clients were Solaris/linux, with a network administrator who knew what he was doing. The performance was excellent and clearcase really made a difference to the teams productivity. It was certainly better than CVS, which it replaced. Actually, comparing clearcase to CVS is like comparing Matlab to a 5-dollar pocket calculator.
2) My current job, where the vobserver is on Solaris, but all the clients are Win2000, with a drooling windows monkey for a network administrator. While the clearcase GUI on windows is excellent and much better than the unix equivalent, its performance is infinitely worse, with the performance of a view degrading in proportion to the amount of time the windows machine on which the view was created has been left turned on. Finally, we instituted a policy that all win2K machines have to be rebooted every monday morning.
It would be aweseome if IBM would make rational release a linux/unix GUI that is comparable to their windows version.
Magnus.
Point for ClearCase, though how many people really take advantage of this feature (we do not).
A large number of ClearCase installations use MultiSite. It works very well over unreliable networks (I currently use it with a VPN between the US and India) or with no network at all (before we set up the VPN, we did updates via sneakernetted CDs). It also aids in disaster recovery because you can physically destroy one site without affecting any of the others. Lastly, it makes backups dead easy to do.
4. Built-in triggering system for file check-ins and check-outs. This allows you to build scripts and such to do things when you check out/in a file or set of files.
I think you can do that with CVS too.
Almost any ClearCase operation can have preop and postop triggers attached to it. The last time I looked (about six months ago), there was a very limited set of CVS operations that could be triggered, and expanding that set was near the top of the to-do list.
6. Smart 'make' routine which can take advantage of compiled object files in other people's views.
Oh yeah, I'll bet a LOT of people really make use of that one.
In very large (>5 million LOC) projects, ClearCase's wink-in facility is essential. With something that big, you can't just work on your own little corner of things without regard to what the other 1000 developers are doing around you. You've got to be able to regression test the whole thing with your changes applied, and that means building the whole thing.
If your makefiles are written correctly, you get 100% wink-in of everything that doesn't have to be rebuilt as a result of your source changes. If your ClearCase environment is tuned correctly, you can wink in objects somewhere between one and two orders of magnitude faster than you can compile them from scratch, plus you don't have the overhead of initially extracting all the source from the repository.
(Yes, I know about Mozilla. I'm not saying you can't manage large projects using CVS or whatever, but ClearCase has capabilities that CVS could never emulate.)
If you weren't using clearmake and wink-ins on your project, then you were definitely wasting your money on ClearCase.
8. Ability to create branches from the code base for program maintentance, and bug fixing of releases, etc.
Which pretty much defines source control in my mind, again I'd have to give a hand to CVS for much easier branching. I could quickly create branches in CVS whereas in ClearCase it is a Big Deal to create branches, and the SCM people don't like it one bit.
Creating branches in ClearCase is as natural as breathing. All you need is a cohesive branch strategy that you apply across your whole source base, like "I want my version; if that's not available I want the version from the latest official build". The free-for-all "I want 1.1 of this, 2.3.4 of that 5.10.15 of the other" non-strategy will cripple ClearCase, but it will also cripple any SCM practice you try to wrap around CVS or any other tool.
You also forgot that ClearCase can provide build audit trails that are way more comprehensive and reliable than revision strings embedded in the source files. The speed with which that lets me diagnose build failures and related problems wins us back a good chunk of the cost of ClearCase in engineer time savings.
For that matter, the richer set of metadata types that ClearCase provides lets you use know why something happened the way it did far more easily than you could with plan version control.
I've done SCM with a variety of tools for about 13 years now, and without exception, everyone who complained about ClearCase either a) was not using the tool to its fullest, b) was mad because it didn't work exactly like Their Favorite Version Control System, c) didn't know the difference between version control and SCM, or d) was really complaining about having to have any process at all beyond just barfing out code.
There's a new crop of tools coming along that may knock ClearCase off its perch, and ClearCase is far from perfect, but as SCM tools go, it's still the king.