Hacker News new | ask | show | jobs
by adev_ 2388 days ago
> For a Java/Node/Python application, this means changing one line in a docker file, and running preprod/integration tests.

Ironically, the theory contradicts the practice and native code is often the easiest to port on new archs.

I have ported to ppc64be, POWER, armv7 and aarch64 several HPC stacks, it is often the native app made in C/C++/Fortran which is the easiest to port/recompile/cross-compile simply because:

- Their build system has been made from the beginning to handle multiple architectures.

- The compilers for C/C++ are the first thing to be ported and tested on a new arch.

At the opposite, python / node / java embed pretty often native modules hidden somewhere, with hand rolled compile scripts in pip / npm / maven and which are everything excepted robust and portable.

1 comments

This hasn't been the case for most Java projects I deal with, native dependencies are fairly rare. Can't comment on Python or Node.