Have you ever burned your hands by some new and immature technology?

Question

I often hear people saying you shouldn\'t rush into adopting new technologies until they have become stable, tried and tested. There is even a joke on how it takes 3 versions to

Answer 1

For lacking market presence:

• Google's Go
  • Poor toolchain, lacks integration with popular compilers and C.
• Python3000
  • Lacks must-have features: Iterators, cleaned up internals and tidier interfaces are nice for us hardcore users, but the majority want performance, and this hasn't been delivered.
• C++0x
• C99
  • It's been 12 years, and no mainstream compilers fully implement this. Popular projects and niche architectures remain on C89 to be safe.

For poor quality:

• Windows Vista
  • 'Nuff said.
• Perforce
• C++

For lagging behind upstream:

• PyGTK on Windows
• MSVC C support

Note that my listing these technologies in no way suggests that they're no good, I'm a huge fan of all of these (except the poor quality ones). My opinion on being burned by these technologies is first hand (usually me trying to push them as replacements for existing technology, or simply running into barriers after a significant investment has already been made.