My first and only experience with Perl was like this: in 1997, just for fun, I tried to write a program in Perl to turn my Mozilla bookmarks into a website. After a week of not succeeding, in frustration I decided to try Python. In two days I had what I wanted, and programming it was a joy. That sealed my judgement that Perl (and all of its culture) was not for me, so I'm not surprised at all that others might feel the same.
(To be fair, there's a single oneliner that does make life a lot easier: ... | perl -pe 's{...}{...}')
I hope this doesn't come off as argumentative. You said that with Python "In two days I had what I wanted", but another way of looking at it: in a week of not succeeding in Perl plus those two days in Python, you had what you wanted.
I have been using btrfs in raid1 setups over the past years, and have not had any issues. Quite happy with the features (snapshotting, send/receive, adding drives to grow an fs)
Given the correct prompt, you can get the training set almost or completely verbatim [0]. Getting a GPL function is enough for GPLs virality, since you effectively lift the code from a GPL codebase and add to your codebase.
Plus, the stack's latest version contains at least one GPL repository which their license tool failed to detect. So it's not something hypothetical in the first place.
I like the Marathons for the same reasons. Only in cold weather it‘s like the rubber of the tyres gets quite a bit stiffer (more so than other tyres), and provides less grip, just when you need it.
reply