There is no one dictating where levels of abstraction have to get drawn, just that once they're there, they tend to stick. The layers of abstraction between C

There is no one dictating where levels of abstraction have to get drawn, just that once they're there, they tend to stick. The layers of abstraction between C out-of-the-box and the interfaces you would want to use when developing for the web can be written, but as far as I know don't exist. The path of least resistance to development is adopting languages and tools where the niceties already exist. The biggest influence of why the lines get drawn where they are is simply evolution. Whatever tools and problem domains are hot at the same time get married. The two both influence each-other and continue evolving on their own. Which is why the interfaces on a fantastic framework still might not be as nice in C. Once your database schema is autogenerated from introspection, do you want to go back? The stickiness of what tools are right for which jobs means that people developing in C++ tend not to make the most of everything available to them. (It's not C, but better for my example where...) On the other side, when I build things in C++ and take advantage of everything at my fingertips, people still assume I'm rubbing two pointers together to create fire.