Is there any danger in committing to a component library such as SmartGwt or Swing?

Posted by Banang on Stack Overflow See other posts from Stack Overflow or by Banang
Published on 2010-05-12T18:07:14Z Indexed on 2010/05/12 18:24 UTC
Read the original article Hit count: 276

Since February this year I have been working on an app that's built using SmartGWT components. Generally, I find the components very nice to work with, and the fact that they're open source and free to use is just fantastic. However, I can't seem to shake the feeling that it's not a durable way of developing, but I can't quite explain why. Maybe it's because I know that any minute now the team developing it could decide to stop, which would leave me and my team in a bit of a pickle, but I'm sure there must be something more.

I have been trying to find ways of explaining this feeling to myself, but to no avail. Therefore I turn to you, dear community, to ask if you can come up with a good reason why committing to building your app (that's supposed to be around for many more years to come) using a component library such as SmartGWT is a bad idea? Is there any reason I should just have developed the components myself? Or did I make the right choice when deciding not to reinvent the wheel and just go for what was readily available?

© Stack Overflow or respective owner

Related posts about smartgwt

Related posts about components