Ask HN: What could an alternative to the C standard library look like?

My understanding of compiler history is that before the C standard, compiler vendors created their own C libraries that shipped with their compilers. Code written to be compiled with one compiler likely would not work without modification using another compiler.

The C standard obviated this portability problem, and arguably standardized problems of its own. Functionality that became standardized, such as strcpy and scanf, now considered unsafe and best avoided, is retained for backwards compatibility. Some functions, such as strtok, modify static buffers and are not re-entrant. Manual memory management is still du jour, without any standardized alternatives such as an interface for reference counting.

The C standard also lacks implementations of common data structures and algorithms, which keeps the language light and easy to learn, at the cost of often needing to reinvent the wheel.

C isn't going anywhere. Many lament the unsafety of the language, and for good reason. However, it's often the lowest common denominator in ABI compatibility. The performance and explicitness of C is unparalleled in a lot of tasks. At the same time, it's rather easy to disable the standard library during compilation, and link to a different one.

I've been wondering for a while, has anyone recently (or ever) attempted to create a competing C standard, or language based on C with only a different standard library? What are the pros and cons of such a project? If you could start fresh on the standard library, could a modern perspective and different design choices yield a better language? How different could the result look? Has something similar ever been done with any other language?