For instance strncmp and (especially) strncpy make very little sense with C strings, but make sense for NUL-padded strings.
In other words, "reading the whole string from memory" could be a performance problem, but a less serious problem for machines of those days, compared to using a few more bytes to store the length.
In general, maybe, but we are talking about Borland here, so business logic apps mostly. String size is not a problem there.
Though it was eventually eclipsed by C/C++/Objective-C on Apple platforms, I believe Pascal was the original application programming language for the Apple Lisa and Macintosh, and produced some revolutionary software in the 1980s.
Object Pascal/Delphi certainly enjoyed a fair amount of success in the 1990s.
… with all of them having been developed and run on 32-bit IBM mainframes and other big irons with «lots» of memory (e.g. 512 kB of RAM would have been considered huge in early 70-s).
C, on the other hand, was developed with limitations of early PDP-11's in mind that were often equipped with 56kB of RAM, so null-terminated strings in C was a rationalised design decision and/or a trade-off. Besides, both, UNIX and C started out as a research and a professional hobby project, not a fully fledged commercial product.
Since the internetworking had been inexistent slightly less than entirely, remote code execution that stemmed from buffer overruns was not an issue, either.
Read the DoD security assessment on Multics, https://multicians.org/b2.html
Afterwards you can read from Denis' own words,
> Although we entertained occasional thoughts about implementing one of the major languages of the time like Fortran, PL/I, or Algol 68, such a project seemed hopelessly large for our resources: much simpler and smaller tools were called for. All these languages influenced our work, but it was more fun to do things on our own.
Taken from https://www.bell-labs.com/usr/dmr/www/chist.html
So thanks to their fun, the world now suffers from C strings.
Precisely my point. The definition of fun is up for a personal interpretation.
Basically, no sane programmer in the 90s would be happy with a string type that wasted three bytes per object.