I'm in the same boat. Multiple key apps that I use at the office either work poorly or don't work at all in IE7 (our company portal among them). These apps are all third-party affairs that we don't have any other driving need to update, so they'll continue along indefinitely.
I'm running 2.0.2 on a 3G with no visible issues so far. In fact, 2.0.2 fixed a lot of the app slowness that I was seeing, especially the Contacts app, which previously had a 5-10 second lag when starting. With 2.0.2 the contacts app is usable as soon as it opens up. As for the 3G problems, the 3G coverage in the areas move between is less than stellar, so I typically just leave 3G off.
Of anything out there I think Cloudscape is most similar to Berkeley DB for Java (an in-process DB). The comment about it being a stepping-stone to DB2 could be made about any JDBC-compliant DBMS...IBM just happens to favor theirs;-)
How is the risk of project forking greater than the risk of product obsolesence through buyout? Ask all those folks who've had a software vendor bought out, only to be forced into a 'new' of 'better' product.
Slashdot Mirror
I'm in the same boat. Multiple key apps that I use at the office either work poorly or don't work at all in IE7 (our company portal among them). These apps are all third-party affairs that we don't have any other driving need to update, so they'll continue along indefinitely.
I'm running 2.0.2 on a 3G with no visible issues so far. In fact, 2.0.2 fixed a lot of the app slowness that I was seeing, especially the Contacts app, which previously had a 5-10 second lag when starting. With 2.0.2 the contacts app is usable as soon as it opens up. As for the 3G problems, the 3G coverage in the areas move between is less than stellar, so I typically just leave 3G off.
They probably sent you a new card due to the TJMaxx fiasco. I had a new card and account # forced on me by CitiBank for the same reason.
Of anything out there I think Cloudscape is most similar to Berkeley DB for Java (an in-process DB). The comment about it being a stepping-stone to DB2 could be made about any JDBC-compliant DBMS...IBM just happens to favor theirs ;-)
How is the risk of project forking greater than the risk of product obsolesence through buyout? Ask all those folks who've had a software vendor bought out, only to be forced into a 'new' of 'better' product.
-chris