Yes, think in tablets and how many "history cycles" required. The context of the idea is extremely important.
The lesson? If you have a rough idea about how the future will be in some domain start to build today. The difficult part of this is knowing what to build. For example, you need a fancy rich UI for your application but there are no components for that so you start building your own GUI library BUT at the same time juggernauts like Adobe, Sun, Microsoft, and Google try (in different technology eras) to move forward with Flash, Java, Win32, Silverlight, WPF, and HTML5.
What is the correct decision? Waiting like a Confucian can be the best option.
The lesson? If you have a rough idea about how the future will be in some domain start to build today. The difficult part of this is knowing what to build. For example, you need a fancy rich UI for your application but there are no components for that so you start building your own GUI library BUT at the same time juggernauts like Adobe, Sun, Microsoft, and Google try (in different technology eras) to move forward with Flash, Java, Win32, Silverlight, WPF, and HTML5.
What is the correct decision? Waiting like a Confucian can be the best option.