Welcome!

[izibi]

Some information about different webframeworks like Django, Ruby on Rails, CakePHP, ... would be cool. Maybe some short tutorial how to create a little application.

[GeoEgo]

It seems a little scary to discuss specific frameworks and pieces of software, as it can date a book quick. However, what about some discussion on the overall idea of frameworks, pros and cons, etc.? Maybe what makes one successful (or not), or where they need to go in the future?

[ByteBros]

But it would be of interest to have a comparisation of the "major" frameworks, isn't it?

[lauragua]

.. as it can date a book quick.

a thecnical book - by definitions - when left the printer ad reach the bookshop it is already old.

[ajcates]

I think a web frameworks section would be great. You can describe the benefits of using a framework and what makes a good framework. Then you can list each framework with it's goals, history and current state.

PHP Frameworks:
CodeIgniter - http://codeigniter.com/
CakePHP - http://cakephp.org/
Yii - http://www.yiiframework.com/
Symfony - http://www.symfony-project.org/
Zend - http://www.zend.com/en/

Other:
Ruby on Rails - http://rubyonrails.org/
Django - http://www.djangoproject.com/
Catalyst - http://www.catalystframework.org/

[GeoEgo]

a thecnical book - by definitions - when left the printer ad reach the bookshop it is already old.

A technical book may be "old" by the time it reaches the bookshop, but that does not mean it is dated. The authors can control the lifespan of the informational relevance by focusing on broad topics and principles that are underlying to specific technologies. Excellent books on the fundamentals of typography and design are given to graphic design students that are thirty years old and more -- they deal with ideas and techniques that stay the same regardless of your technology. I'm not saying there should be nothing mentioning new technologies, I'm saying that the content should be included sparingly and cautiously.

Personally, I would rather read an article about the principles of grid design than a how-to on the 960 framework, and long after 960 ceases to exist, I can take that knowledge with me.

[earthwormjim]

I'd have to agree to with those opposed to this idea (no offense to you, izibi). The web is made for manuals. A book is something to display and show your friends. A book by Smashing even more so. Think of all the great visuals this site has brought its audience. Does a book bearing the name deserve to be striped in lines of code?

This is coming from a web programmer.