It broke on the simplest of fields, and I spent more time messing about with it than I was working on my install profile.

I also recently had had enough of working around cck's deficiencies for my project, and started rewriting all my content types into standard drupal node types. Which in turn has made the code a _lot_ cleaner, and has given me sufficient control that I didn't have to do anything "hackish" to make it all work together (such as fields that should not have any user interface elements, as they are exclusively backend). It also made about 9 dependencies just go away.

And the upgrade path is also now completely clear. And everything is cleanly versioned. CCK was incredibly useful for prototyping however, but in the end it was just saving me from implementing 1 CREATE TABLE statement , 5 sql statements (insert, update, select, delete, delete revision) and 2 elements per field (input and display). Even views integration isn't that much extra work. It's basically ~ 100 lines of boiler plate code with a few details slotted in (see node_example.module).

In my experience, CCK is less work for admins, but more work for developers. Guess who's time is more valuable.

Also. you can override module provided views, but then you lose the upgrade path and versioning.