Currently the state of DBIx::Class is perfect for a long term project - it isn't changing, and it does tons of useful query generation.

DBIx::Class does have some bugs in the design, and does have some misfeatures, but at this point fixing any of them would break back-compat, and the people with decades-old projects would most likely prefer that it remain stable. As an everyday user of DBIx::Class, I'd say its biggest problem is the learning curve to onboard new people. Clearly that isn't a bug that can be fixed without breaking back-compat :-) To make it nicer to use, I suggest DBIx::Class::Helper::ResultSet::Shortcut and my own DBIx::Class::ResultDDL.

It's a terrific force-multiplier if you have large complex dynamic queries to write.