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

I was once forced to used witango, but I'm getting over it.

Answer 2

VBA - We spent a lot of time integrating it into our product. We still spend a lot of time on each new release to make sure that we don't break anything. VB6 and VBA is also COM based and that is a problem if you want to run as a standard user and not have write access to the registry.

Answer 3

When I was 10, my father tried to play a New Year song for me on a brand new Elektronika BK-0010-01.

Needless to say that the synthesizer failed to load from the tape and there was no song until the neighbour came with a guitar.

Answer 4

Anyone noticed the trend here? The majority of technologies here were created and canceled or modified by microsoft...

I also have been burned by microsoft with changes made to the entity framework.

Answer 5

Several years ago, we made heavy use of the new SQL Server 2005 feature called Notification Services. To our dismay, that has been discontinued in SQL Server 2008. This was a serious problem, caused the software architect to question all new Microsoft technologies.

Here's some detail and some more and some more

There have also been issues with Microsoft's Entity Framework.

Answer 6

Java

I was very eager to start working on it in 1996 and used it for several projects. But for web development I always preferred Perl and these days PHP. GUI development I ended up mostly using .NET. For the few command line programs that cannot be handled by scripting I prefer to use Perl, Python or even for that PHP.

Few of the Java programs I wrote were used over long periods of time, while some of my pre-java applications are still in use.

I think the main reason for this is that it always took longer to develop something in Java than using another programming language: so the resulting applications contained less features and were easier to replace.

As speed of development is usually an issue for my customers Java tends to end up as the second choice.