While I wasattending a training in ASP 2.0, and experiencing with the new controls (Web Server controls, the calendar for example) versus the classical HTML controls, I have noticed that when some service/function is found to be of a common interest among people, it will be defined as a built-in service/functionality in the next generation.
The life-cycle will go like this:
built-in functionality1 provided –> many people will use it in building common functionality2 –>
in the next generation functionality2 is provided as a built-in.
Posted by free2blossom