Le blog d'Arhuman

Many of my friends express their surprise when I say I chose to learn JavaScript in 2016. With so many cool languages to learn, why using a "toy language" of the past instead of, let's say Haskell, Go, Nimrod, Rust (just to name some)? First and foremost, for me it's not as much as learning JavaScript in 2016 as learning a new language in 2016. But whatever your reasons : not become fossilized, improve your efficiency with new tricks/paradigms/tools or just plain fun you'll probably feel the urge to learn a new language sooner or later. This bring us back to the question why JavaScript in 2016? Reason to choose JavaScript Ubiquity It could be handy to be able to do everything in one unique language (from command line tools, front-end Web dev,  server coding, phone applications to robots programming) and JavaScript now allows that. That wasn't the case before but with node/express/commander/ionic/cylon.js (to name few) you'll have all your needs...

Once again I have to handle the same situation : no more spaces and directories with a lot of duplicates. That's not the first time I have to do it (last time it was to remove all the duplicates .mp3 with different names when I merged my various 'Music' directories from different boxes/disks.), so I already have a small script waiting in my repos. But this time I choose to explore another way, instead of removing duplicate files, I've tried the hardlink substitution way. Using hardlinks is not always applicable but my perl5/perlbrew directory seemed a good candidate (read only duplicate data...). And it was : after running my script on it, the size went from 765M to 670M, and all the test suites of the tested modules passed with all the Perl versions. I first thought to release the script as a patch for perlbrew, but thinking more about it I realized that a need probably exists for a more generic tool. That's why App::Phlo was created :-) Not a killer ...