What's wrong with delicious.com?

The recent UI changes of delicious.com is quite confusing and smells suicidal phase. I have noted that, after Joshua Schachter sold it to Yahoo!, it's going crazy changes. Probably, it's because a Yahoo! company now or Engineers don't get the real idea?

Some crazy moves:

del.icio.us to delicious.com change; probably to reach countries that censor .us TLD?

delicious.com to www.delicious.com; unjustified

Perl to PHP switch; why?

for:handle geekish way to share to separate box; crazy but ok. Looks like, the new Yahoo! guys don't know how to make it a cult following like how twitter popularized @handle

Recent broken UI

Comments

I'm Zend (PHP 5) Certified Engineer:-)

As of January 13, 2007, I'm ZCE/ Zend Certified Engineer (PHP 5)

"PHP 5 Power Programming" Free in PDF

The book PHP 5 Power Programming is now available free of cost in downloadable PDF format at Bruce Perens' Open Source Series promotion site. Along with this book, a lot of other books are also available there for free! Details ISBN: 0-13-147149-X 2005. Pages: 720 Authors: Andi Gutmans , Stig Sæther Bakken , and Derick Rethans Download location: Perens Series Page (PDF) License: Open Publication License File size: 9.6MB Original price: $39.99 Edition: 2005

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...