4 ms·
Performance is the least of my worries here. I'd be more worried about security, and plain dependency management. I mean, let's say this libc thing is supposed
by nandemo 12y ago
Performance is the least of my worries here. I'd be more worried about security, and plain dependency management.
I mean, let's say this libc thing is supposed to be installed in quite a lot of systems, are we really sure that perl thing is installed in all of those systems? And what if, by some crazy coincidence, perl happens to depend on libc?
- derefr 12y agoIn Debian, at least, there's actually a number of circular dependencies within the (small) set of packages marked as "essential"; they all sort of lean on one-another like a house of cards. Perl is in that set, if you're wondering.
- ryanlol 12y agoAlmost everything depends on perl. Unless you're running a very small embedded setup, you'll have extremely hard time living without perl. Circular dependencies are perfectly normal.
- nandemo 12y agoI'm aware that a lot of projects use perl for the build. But on runtime? I doubt it.
- merijnv 12y agoIt's Apple's libc. They ship always ship Perl on OSX (and presumably iOS too?), so what do they care whether other platforms have to deal with an extra dependency? Their platform has Perl anyway, so the dependency is essentially free.
- ryanlol 12y agoAre you on a Debian based OS? Try aptitude search '~i~Dperl'
- comex 12y agoApple libc in particular is supposed to be installed on exactly two base systems: OS X and iOS. The former has perl installed by default, and the latter marks wordexp as unavailable.
- vertex-four 12y ago> I mean, let's say this libc thing is supposed to be installed in quite a lot of systems Apple's libc is not an independent thing to them - it's a part of OSX and iOS. You're not supposed to be able to take it out and use it for other things.
- nandemo 12y agoFair enough.