I think grids are a major problem, unless presented read-only to provide context for a current-row edit.
If you let the designtime only tools handle everything yes. But as said, most big applications don't, even if only they want to have more control over transactions. IMHO it is unfair to compare Delphi/Lazarus level 0 (all design time, without much errorhandling) to fully blown business apps without context.
And still you can get pretty far quickly with level 0. I have done pretty serious database apps in a previous job, but in our current very small job I happily use designtime components. Time saver, and the connection problems are not that important in this age of fiber to the home, and with 1 1/2 user there is only transactional security on certain main tables.
I agree, and I'm not necessarily hostile to that. However I'd like to backtrack and highlight Thaddy's blaming of the Tories (the UK's right-wing party) for the PO debacle: historically, all major parties tried to favour ICL, with the Tories possibly less to blame since their approach (if given free reign) would have been to divest the state of all involvement and favour the market economy.
That is a dud too. Any one who took some economy classes knows that the classic market economy has certain border conditions (like many producers and many consumers which can't influence price on their own). Only in those conditions you really get "market" conditions. In privatisation scenarios those rarely hold true.
Basically it is just washing their hands so they can blame the "market" if it fails, while making sure their cronies get a updated salary "according to market standards" for as long as it lasts.