Re:How I implemented my own crypto
by SmallDeadGuy on Thursday August 03, 2017 @04:43AM
(#14917951)
I would argue the other way. Something which requires a base implementation to be installed on a system which generates different machine code based on a single specification is less portable than a macro processor generating different versions of a program. Sure, people will have had something like python installed since a long time ago, but a new setup requires downloading 2 objects (the base implementation and the program) compared to a single one (a platform-specific copy of a program).
[ Parent
| on HN ]
How is the deployment of a high-level runtime different from libc? Both can be statically-linked if required.
Re:How I implemented my own crypto
by reikonomusha on Thursday August 03, 2017 @04:47AM
(#14917962)
You still need to download two objects: the C code and the C compiler, even if the C code has already been processed.
Edit: Not to mention libc, libm, and the like.
Re:How I implemented my own crypto
by SmallDeadGuy on Thursday August 03, 2017 @05:00AM
(#14918024)
You don't need a C compiler to run an already compiled program. You may need libraries, just like almost every language, but only the developer needs to download the compiler and not every single user.
It gives options to the developer to target multiple platforms without extra effort from the users of those platforms.