Yeah, the syntax was like that.
I think you might be right in that the compiler didn't enforce the types at the point of the call. But I'm still fairly sure that a type mismatch was undefined behavior, and if you somehow got it working, it would not be guaranteed to be working henceforth. It was certainly not just one parameter = one word, since K&R already had long and float and double, and those would normally be wider than a word on most machines of that time
So basically, types were always there, but type checks weren't.
When they added ANSI-style function declarations, you could actually have parameters listed with their types, and that was checked... but for compatibility they still retained the old-style function calls without seeing the definition, where you had to match the arguments carefully.
Unless you have fairly narrow requirements, and want a generic Unix-like server or desktop, you'll almost certainly have best luck with FreeBSD (in terms of software availability, hardware support etc).
MATE? Xfce? LXQt?
The nice thing about text logs is that, even if they are corrupted at some point, the rest of the log is still perfectly readable.
You're missing a cloud solution here.
Most of the "streets" on that map are actually parking lots - naturally, those aren't public. But there's still plenty of public streets, and yes, checking Google Street View coverage is a good way to see what they are. 157th / Microsoft Way, for example, is public, and goes right along a bunch of buildings. Ditto 31st, 36th, 163rd etc. 150th is right next to the Mixer, which is where a lot of 'softies go to have lunch, and on the other side of that there's 40th.
We want to create puppets that pull their own strings. - Ann Marion