I saw this on Facebook the other day. In other news, Mom's cat "Fuzz" puked up a furball this morning. It was not uncommon for unattended DOS systems to run for a year or more. Three months is not news. When WIndows became more popular so did rebooting. I think the only thing that was a native problem with a DOS system sitting idle was if it didn't make a system call. The internal calender date would not advance until a system call was made so the calendar would stop if sitting at a DOS prompt. It would not know if the clock passed a second midnight. But most systems were doing something if they were left on, so it wasn't really an issue.

jlongo wrote: when they designed Swift they could have just used the ECMA C# standard— and saved a ton of money on language design by using a language designed by people who know how to design a language and that is 20 years mature As a C#-Forever developer I totally get what you are saying. I know that Swift has to interact with the underlying NS (NextStep) classes / objects and I think they had to do a lot of work there so all the extra work probably became one of those, "well, let's just roll our own" kind of situations. Also, (the most difficult thing about learning Swift) is the fact that there is so much declarative code (versus imperative-type coding that is done in other languages) and I think that is something the Swift creators were also trying to achieve -- but it makes the language like magic for me a lot and magic is hard to learn, because you just have to accept it that it does it.

v1 - CodeProject[^] M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

Interesting, thank you. Paul Sanders. If I had more time, I would have written a shorter letter - Blaise Pascal. Some of my best work is in the undo buffer.

Hmm, I guess there was no monitor connected to the Mac. I know when I remote connected to a Windows PC without a monitor it caused issues with the remote software. If you need to go back to remote desktop software you could try a monitor emulator dongle (AKA HDMI dummy plug) to simulate a monitor in hardware. Software-wise I use TeamViewer - it is free for personal use. It can work over a local network, although that is not the default.

Win16 did a lot of thunking. I remember it as a little ASM code snippet mostly used to adjust the CPU DS (data segment register) so that when Windows called back into your code you had access to your “static” variables that lived in the DS. Something similar happened when using DLLs. Each DLL entry point would adjust DS, A bit foggy now! I do NOT miss it. If Win16 was still in use today, ransom ware vendors would be billionaires!

I look forward to your apps created with your new Mac Mini.

It depends on the language. For JavaScript and TypeScript it's camelCase. For C I'll use all three depending on my mood and the project. As an aside, I too want to like Rust, but its opinions are a bit too opinionated. While I understand the reason they chose snake_case for a systems language, I just can't help but feel that's an old convention for what's supposed to be a modern language. At the very least, it shouldn't be a compiler error if someone wants to use something else. Jeremy Falcon