> /me wonders how people work on a devel machine without mlocate :)
Let me try to explain why I'd never heard of mlocate. :)
We run the identical version of Perl with an identical set of CPAN modules on our many different Unix boxes (multiple versions of: AIX, HP-UX, Solaris, Red Hat Enterprise Linux (RHEL), Digital UNIX, Tru64 UNIX, IRIX, UnixWare, SCO Unix, ...).
-- from Re: putting perl and modules in your source code repository
When your typical work day for over twenty years has been spread across Windows boxes and many different Unix flavours, you naturally lean towards standard POSIX commands (such as find and xargs), rather than system-specific ones (such as locate/mlocate), because you know they're available out-of-the-box everywhere.
Better, as indicated at Unix shell versus Perl, is to avoid a motley mix of Unix shell and Windows batch scripts by writing everything in Perl ("It's easier to port a shell than a shell script").
If I had a job where I spent most of my day on a Linux development machine, it would make sense to invest considerable time in mastering Linux-specific dev tools (interested to learn BTW if you get to spend most of your work day beavering away on a Linux dev box).
Now that I know about mlocate I might get around to installing it at home on my Ubuntu VM - more likely if you, or some other kind Perl monk, sold me with some examples of how it makes development more enjoyable. :)
Updated: minor changes to wording.
👁️🍾👍🦟
In reply to Re^4: uparse - Parse Unicode strings (locate/find/xargs)
by eyepopslikeamosquito
in thread uparse - Parse Unicode strings
by kcott
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |