3 ms·
> You also need any supporting infrastructure that the libraries used will need. This will also be true of a program in a compiled language, so I don't see tha
by pdonis 6y ago
> You also need any supporting infrastructure that the libraries used will need.
This will also be true of a program in a compiled language, so I don't see that it differentiates between different languages.
- taeric 6y agoI felt I was progressing your point. You can't answer if a program is portable based solely on the language.
- throwaway894345 6y agoYou’re referring to a different definition of “portables than the concept TFA appears to be describing. Within the scope of TFA’s definition, a language (or more precisely, an implementation) absolutely can be portable. Any implementation that can bundle all dependencies (including the runtime) into a single artifact can said to be portable per TFA’s definition of the term. Python could even be portable in this sense if it could zip up the interpreter, libraries, and all so files (however, these bundles would be hundreds of megabytes compressed in practice).
- taeric 6y agoBut that is a shit definition. :) Portability has to take into account the scope of where it will be ported to. And, often, porting the software is something that has to be done. It will not be an intrinsic of the language or the program, but work that was done for them. Is why SCUMM is probably the most ported software. Was not necessarily an intrinsic property of the engine; though, it clearly had affordances that helped. Really, I think Linux shot down a large part of the portability debate. It was made to be non portable. And now it has been ported everywhere.
- throwaway894345 6y agoAgain, I think you're just insisting on evaluating the article based on your own definition of "portability". Note that I agree that your definition is more standard, and the confusion is attributable to the author choosing to overload that term. Let's imagine that the author used a different term--say, distributability--and defined it as something like "how easy it is to get cross-platform software up and running on another system" and the context is "desktop and server computing" as opposed to embedded or whathaveyou. I think this is a perfectly useful criteria for evaluating programming languages (which isn't to say that it's the most important or even very important, only that it's useful). It's useful to know whether I'm going to have a very easy time distributing software (e.g., a self-contained static binary) or a very hard time (e.g., I need to get my non-technical colleague to install brew, use brew to install the right version of python, create a virtualenv, install dependencies--probably including various C dependencies that pip doesn't know about, and then install my application). This isn't a hypothetical consideration; it's an important consideration for me whenever I'm creating internal tools. However, to your point, this isn't helpful for figuring out which languages are going to be able to be deployed to the widest breadth of architectures. They're simply different ideas.
- taeric 6y agoFair. I get what the article is aiming to talk to. I would still pull up Linux as a fun counter example. One of the more ported code based ever. Not even really portable between compilers of the language it is written in.