News for hackers. Stuff that matters.
Re:The C juggernaut illustrated (2012) by WalterBright on Saturday February 04, 2023 @07:00PM (#34659897)
UCSD Pascal was too slow to be competitive.
Re:The C juggernaut illustrated (2012) by AnimalMuppet on Saturday February 04, 2023 @10:27PM (#34661501)
Was it Pascal in general that was slow, or just USCD?

Was that the p-code system? Or was it a true compiler? Was it slow because it was p-code?

I wasn't on UCSD, but I don't recall Pascal being particularly slow compared to C. I never benchmarked them against each other, but it wasn't noticeably slower to my eyeball.

Re:The C juggernaut illustrated (2012) by WalterBright on Saturday February 04, 2023 @10:43PM (#34661602)
It was slow because the P-system was an interpreter, not native code. Java fixed that problem with the JIT. (Steve Russell created the first JIT for Java, and the result was spectacular.)
Re:The C juggernaut illustrated (2012) by fsckboy on Friday February 10, 2023 @01:50PM (#34743952)
that's not entirely true, for example, Microsoft Word for the Mac (and PC) was p-code C, because p-code is a lot smaller. I think UCSD pascal was, yes, slow because of p-code, but also pascal is a very limited language compared to C. P-code with pointers is going to be a lot faster than p-code with no pointers.
Re:The C juggernaut illustrated (2012) by mistrial9 on Sunday February 05, 2023 @01:24PM (#34667313)
the Apple compilers were good enough, with a lot of ASM.. the other comment is trying to change the subject to Sun things, which is like England vs France topic