4 ms·
Hmm, maybe this is a dumb question, but Numpy, Pandas, Scipy, etc are all libraries. Are libraries considered tooling? When I think of tooling, I think of linte
by bee_rider 4y ago
Hmm, maybe this is a dumb question, but Numpy, Pandas, Scipy, etc are all libraries. Are libraries considered tooling? When I think of tooling, I think of linters, debuggers, IDEs, and so on.
I can definitely see why libraries should be written in faster languages, they are used all over the place. And anyway, something Numpy is most importantly an interface to pre-existing high performance libraries (BLAS, LAPACK) which were already written in faster languages.
I think it is less obvious that a tooling in the second sense should be written in a lower level language. There's the obvious flexibility tradeoff, the fact that a person interested in a linter for a language probably is most familiar with that language.
I'm not familiar with the computational problems in linters. Is getting better CPU performance a huge concern?
- cercatrova 4y agoA linter like Prettier can take several seconds in large codebases while the one by Rome (rome.tools) takes fractions of a second, because the former is in JS and the latter is in Rust. If I'm a linter user, I really don't care what the linter is written in, because I'm never going to open up the source code to look at it. It likely exposes a configuration file which is agnostic to any programming language, and that is what I will primarily be editing. Same thing with Webpack vs esbuild or swc, the latter two are simply instantaneous while Webpack can take minutes, even, to build an app. That it's in JS does not matter to me since I don't care about Webpack source code, I only care about what the tool itself does.
- SAI_Peregrinus 4y agoIs a compiler "toolchain" package tooling? Is the standard library included with that "toolchain" tooling, or a library?
- bee_rider 4y agoSo, I don't think it is really necessary for there to be a perfectly bright line between the two. But for the sake of argument, I'll say that my opinion is that the compiler, linker, etc are part of the tooling, while the standard library is a library. All of the libraries are linked to the project by some tooling, and a particular distribution of software could include any number of libraries (e.g., conda), I don't see why the standard library needs a special cutout. It will get even more blurry if you start asking about runtimes, macros, and all-template libraries.
- SAI_Peregrinus 4y agoOften (parts of) the C standard library (those needed for a freestanding environment) are actually "baked in" to the compiler, and not actually separate header files at all (though equivalent headers may be provided as well). In C89, those are float.h, limits.h, iso646.h, stdarg.h, and stddef.h. C99 added stdbool.h, and stdint.h. C11 added stdalign.h, and stdnoreturn.h. So those headers are part of the standard library, but they're also usually part of the compiler. The line gets very blurry.