446 karma · joined February 13, 2011
A 'fake' SMTP server that just saved the e-mails to the file system as plain textfiles helped me to find the error before I actually sent the mails out. I am not entirely sure but I think it was this project: http://sourceforge.net/projects/fakemail/
For more nostalgia, a large collection of cracktro remakes in Flash can be found here: http://flashtro.com/
Seems that Ruby had one good standard solution with gems for a long time, let's hope that Composer has a similar bright future. From my perspective, it's already the standard and including a composer.json file is a 'best practice' for all 'well-connected' PHP developers releasing a library these days.
http://getcomposer.org/doc/05-repositories.md
I don't know how Bundler handles this and it probably isn't even needed, as gems are just the standard in Ruby but PHP didn't really have a standard besides PEAR and Composer brings everything together.
I am also often seeing comments about ORMs saying "What's so hard about SELECT..." - nothing's really hard about retrieving data, every decent developer will sooner or later end up with a working complicated SQL that gets them exactly what they wants. But I think the real benefits of ORMs start when you have to save/edit/update/extend relational data again and have to take care of all the inserts, updates, deletes across several tables, maybe including versioning or workflow (drafts or changes waiting for approval) and other additional complexity on top. That's the parts where I am glad to rely on an ORM supporting relationships and which can be extended via hooks or behaviours. (Note that I am mainly talking about 'Admin' pages here and nothing that runs too often.)
That said, I don't see this taking 'months' either, they could just write a wrapper function that mimics the old behaviour and their tests should cover it. If their quality control or inner workflows make changes like this take months, I'd expect that upgrading to a new PHP version and the related testing and QA should take them years.
Not everyone is using Rails though and even the Rails coders might want to use other plugins, are you going to offer themes without all the Rails customization as well?
On a sidenote, I just changed passwords for what was probably my second last.fm account and I haven't logged in or 'scrobbled' since 2007. Different times for sure.
The question is: How would you go on about moving your user database from md5 to a more advanced algorithm? Validate a user's password on log-in and then encrypt it with the new, more secure algorithm?
And maybe it's just me but in order to compare prices, remaining time on an auction and such, I prefer a table or list layout instead of the Pinterest masonry style.
That said, I think I need some kind of short and sweet weekend project too, really longing for the feeling of having something out there, up and running. You already did it, thumbs up!