Clearly this is a valid concern. I also don't like being tied to an Internet connection all the time. For example, I like having browser access to e-mail (so I can check up on things when I'm away from my own machine), but I would never trade the cached off-line access, load speed, search speed, backup and other features that I get with Outlook.
A big part of the issue with modeling is that many of the participants in the modeling process--both modeling experts and domain experts--are not developers, so requiring a heavy-weight development tool to create, view, discuss, and share models with all participants in the process can be a major stumbling block. Microsoft effectively killed the Visio-based ORM tools by packaging them in high-end, developer-targeted Visual Studio box. Simply put, we need to make it easier to use ORM models across a wider audience.
Of course, the broader availability of ORM is also the gist of your original query. I fully agree that we need broader access, and that developers and development tools are a big part of it. However, I also think that focusing too much on the back end technologies obscures the vision of where we want to be. The goal is to be able to design, implement, and execute at the conceptual level, with the backend becoming less and less of a concern over time. I think web-based technologies offer ways to approach this problem in a way that local apps and development tools can't touch. I'm not sure I would have said that five years ago, but the world is changing both in terms of connectivity and in the client-side browser capabilities.