Luddites were a social movement who protested against the Industrial Revolution and protested against technology. They prefer "the old way" of doing things.
Many PlainCee? programmers are like Luddites. Some plain cee fanboys resist new technology because it isn't plain cee. They think everything else is bloatware; plain Cee is king to them, because C is simple. I'm not a huge fan of C++ since it is a complex mess of a language, but at least C++ has strings. One can be disciplined enough to use a subset of C++ and not all of it.
PlainCee? doesn't even have strings. It only has pointers to chars. This is primitive and anti-technology, as are Luddites. Anyone who prefers using pointers to chars over strings (like in PHP) is a luddite that resists improvements to our technology. You could still have a Cee like fast language with strings, such as GoLanguage.
Why C is Obsolete (by the completely unbiased ;-) author of CeePlusPlus, BjarneStroustrup):
Sometimes the old way is the best way. For the uses for which CeeLanguage was intended (systems programming, embedded systems), there is still no better tool. For other tasks, where programmer time is more important than processing time and memory efficiency, a more convenient language like Go, Python or shell script can be more appropriate. HorsesForCourses.
ATS Language is a better tool than C for the tasks for which C was intended.AppliedTypeSystem does look like a promising research language. The page of examples tackles many areas where provability would be an asset. I'd also like to see some work on cross-compiled embedded targets. I hope the author has a plan for world domination; too many of these research languages die after the thesis is written.
Plain Ol' C is still the language of choice for creating most EmbeddedSystems applications these days. It's equivalent to a super-assembler; you have access to the machine down at the metal but can stay away when you don't want to get too messy. The stuff that needs to port can do so, and the stuff that needs to tie to a particular piece of hardware can do that. C will die when the Earth's core cools off.
Being there first is a significant advantage - but one measured in decades, not millennia.
Yeah, um, order of precedence isn't the factor here. C is the tool of choice when creating hardware-based systems because of its close-to-the-metal capabilities. More brain power has been spent optimizing C compilers than everything else combined over the last twenty years or so. Other language systems are great for other application spaces, but when you need to make an electronic gizmo do its thing then C is still your first choice, every time.
No matter what language you use, there is always a risk of obsolescence. If the language does what it does in its niche fairly well and a significantly better replacement has yet to come along, then stop worrying about obsolescence and use it. The "in" language rarely remains in for more than a decade, and probably the average "in" time is more like 5 years.