My first dev job was with a civil engineering consultancy that also built a suite of tools for hydraulic modelling, geo-spatioal and logging and telemetry use cases. We used the IBM ILOG JViews framework for a lot of our software and honestly it was a pain to use and clunky as hell.
The worst thing though that was despite paying an inordinate amount of money to license this software each year and receive support for it they would not fix a bug we found in their mapping modules.
Specifically it was their use of float for X and Y coordinates in the IlvPoint object that you pretty much had to use to make a map work with their tech. In certain parts of the world there is an extra digit on the Y coordinate (projections) and the float they insisted on using couldn't store the whole value, meaning they would just round it up or down causing inconsistencies between our representation of a client's dataand the client's representation. That was an absolute no-go for us and the workarounds IBM suggested to us were absurd and bordering on insulting honestly.
We had a lot of trouble with our affected clients because of this and all we could tell them was that it was an IBM issue.
The absolutely refused to fix their product and eventually sold it to Rogue Wave, washing their hands of it. By that point though we had already decided on a few alternatives lest we start to lose customers (who were essentially massive utility companies from around the globe).
The worst thing though that was despite paying an inordinate amount of money to license this software each year and receive support for it they would not fix a bug we found in their mapping modules.
Specifically it was their use of float for X and Y coordinates in the IlvPoint object that you pretty much had to use to make a map work with their tech. In certain parts of the world there is an extra digit on the Y coordinate (projections) and the float they insisted on using couldn't store the whole value, meaning they would just round it up or down causing inconsistencies between our representation of a client's dataand the client's representation. That was an absolute no-go for us and the workarounds IBM suggested to us were absurd and bordering on insulting honestly.
We had a lot of trouble with our affected clients because of this and all we could tell them was that it was an IBM issue.
The absolutely refused to fix their product and eventually sold it to Rogue Wave, washing their hands of it. By that point though we had already decided on a few alternatives lest we start to lose customers (who were essentially massive utility companies from around the globe).
Fuck IBM.