[the_arun]

Very opinionated list of thoughts. For eg. >> often ‘playing with a new framework’ doesn’t solve business problem.

May be we could re-articulate that as - Nothing wrong in playing with new frameworks as long as it results in improving the product.

[mannykannot]

I am fine with it the way it is, as I have seen too many 'ego' and resume-padding projects justified by nebulous claims of benefit. I was looking at a case recently, where the use of a fashionable database engine, sold on making the application more fault-tolerant in ways that did not really matter, instead impaired the exploitation of its innate parallelism.

It is not difficult for the nominal technical expert to guide a client into choosing the solution he wants, rather than the one the customer needs.

[collyw]

He seems to miss out that everything is a trade off.

Sure playing with a new framework may not meet the initial business needs, but it may be worthwhile in the mid to long term. Learning Django for me has paid for itself multiple times over in terms of gained productivity.

> "Every new successful framework is a step in interesting direction, so think about ‘what does this framework/library change about my work’"

I am not sure that is actually the case, especially with front end frameworks.