Hacker News new | ask | show | jobs
by user5994461 2186 days ago
I want to say Oracle database clients as an example.

My company definitely had problems to get database drivers to work generally speaking and on both 32 bits and 64 bits. Have a look at postgres, oracle, cassandra, redis, sybase to name a few, I am not sure which one was worse, it wasn't me doing the work. But I've seen some of the C and C++ dependencies that needed to compile with the errors that happened and that was horrendous.

3 comments

Fair enough — I've used Oracle's products enough to know that software distribution and packaging is not a priority there.
I've been using postgres, cassandra, redis and mysql/mariadb on aarch64. Only ran into issues with MySQL, which we rootcaused to some weird atomic locks not working as expected on the first generation of ARMv8(.0) a couple years back.
That’s a good moment to make your c/c++ code more robust, and cross-platform, like the languages they are
The problem wasn't in our code, it was in the database code that was either from open source or from a vendor.

If you want a sample. Try to install the cassandra client library in python. It will pull in and compile all sort of shit. That's supposed to be python and easily cross platform.

Yes, so time for them to clean up their mess ;)
Reading the comments here flow something like this: 1. complain that switching to ARM is a mess 2. no it's not a mess, it's easy 3. no, see it's a mess 4. fine, clean up the mess.

Yes, we should clean up the mess! It doesn't mean it's not a mess. And I think the mess is actually still understated.

I think it will come down to PRs accepted. So it's your mess in the end as it depends on the companies strategy.