3 ms·

I agree the companies are unlikely to rework the current code from Oracle to PostgreSQL (or some other database), but they'll definitely think twice when starti

• philipov 10y ago
  When managers start a new project, they don't want to think twice. They want to grab the ass of someone else in the company who's already done the same thing and leverage their expertise to reduce the cost of the project. My company is still stuck using CVS because when a new project starts up, they want to use the people who are already locked into the old tech and so they end up going with what people already know. Even teams that started with git have downgraded to CVS once the managers starting looking for ways reuse resources.
  • pgaddict 10y ago
    It's always a cost/benefit evaluation. When the costs stay roughly constant, the outcome is usually to use the same stuff as for previous projects. But when the vendor significantly increases the costs, like Oracle does in the recent past, that may have significant impact. It may be easier/cheaper to switch to a different database, for example. I'm not saying all companies will end up doing that, but some certainly will (and already do). They may not be vocal about it, though, because they don't want to piss Oracle.