Sure, caching offline doesn't NEED email. But emails servers have been doing it since the dawn of time. So now we have to reinvent the wheel.
I finally got around to installing perlbrew, 4 flavors of perl and updating some modules for recent perls. I've been sending a lot of email test reports lately.
Last night I got the email from bitbucket about CPAN Testers 2.0 and the death of sending reports via email with wiki links/instructions on how to setup
I need to build a site for a local organization. Since they need to edit most parts of it like a blog, I'm using WordPress and creating a custom theme/categories, etc.
Overall, I love WordPress. The API docs are awesome; look good, easy to read, plenty of content and examples.
Quite literally.
http://use.perl.org/search.pl?op=journals
Hasn't worked in two weeks. Totally devoid of results and the front page looks bare.
Rather than fix these things, I think it's time someone just shut off the site entirely. Seems like the kind thing to do, like putting your pet to sleep to stop the misery.
This is an awesome resource: http://guides.rubyonrails.org/
Yes, CPAN has a wealth of information...now it only it was presented like this or our frameworks had something this good.
rubycritic...or rubytidy
And while I'm at it, where's perls Rake? imho, it kicks Makefile.PL in the ass sometimes.
Looks like it comes with 5.10.0:
http://michaelflux.com/snow-leopard-10a380-notes-of-interest
Here's hoping it at least has the patch for the nasty stock 5.10.0 @_ assignment performance hit.
Fresh install of OSX last week. Totally forgot about local lib before update the sys perl.
No matter, this weekend will be a fresh install of snow leapard, so I get another shot.
Speaking of, I wonder what version of perl comes on 10.6.
I could become one with the Cult of Done. I tend to consider "done" what I've achieved coding nirvana: has tests, has docs, has a clean api... couldn't be done better [at this time] until a major refactor.
I want to collaborate with another using GitHub. Now for the trick: I want to keep that repo on GitHub up to date with any changes made from a source Svn repo.
My first attempt was:
git svn clone
add remote
git pish to github
Of course, and few svn rebases later, I've got jacked up logs ad merge conflicts over and over and over.
I guess I just learned the rule: never use the same branch for svn rebasing and github sharing.
