On Sun, 06 Jan 2013 20:58:45 -0500, Arne Vajhøj wrote:
> On 1/6/2013 8:46 PM, Twirlip of the Mists wrote:
>> On Sun, 06 Jan 2013 20:24:29 -0500, Arne Vajhøj wrote:
>>
>>> On 1/6/2013 7:22 PM, Twirlip of the Mists wrote:
>>>> On Sat, 05 Jan 2013 21:56:37 -0500, Arne Vajhøj wrote:
>>>>> On 1/4/2013 1:44 PM, Twirlip of the Mists wrote:
>>>>>> The concept of a PID is platform-agnostic -- all Unices seem to have it,
>>>>>> MacOS is a Unix nowadays, and newer Windowses have PIDs. It'd be surprising
>>>>>> if there isn't a platform-agnostic way to get at PIDs -- a POSIX call that
>>>>>> Windows supports, most likely.
>>>>>
>>>>> *nix and Windows support does not mean platform-agnostic.
>>>>
>>>> 1. When was the last time you, or anyone you know, bought or saw anyone
>>>> using a computer or other gadget that wasn't either Apple, Windows, or
>>>> some flavor of Unix?
>>>
>>> Yesterday.
>>
>> What operating system was it?
>
> OpenVMS
>
>> Do you think your experience at all typical
>> of the general population?
>
> No.
>
> But the fact that some platforms are not widely known does not make
> them non-existing.
It does make them non-relevant. Planning for them is like planning for
waking up tomorrow and finding that everyone else on Earth has mysteriously
disappeared, leaving you the last person on the planet. It's not
theoretically *impossible*, but it's so unlikely it's not worth considering
unless it actually happens or you have specific knowledge to suggest it's
imminent.
In this case, if you're designing a program for OpenVMS, consider OpenVMS.
If you're designing a program for generic use by the general civilian
population, consider Unix derivatives and Windoze. If you get specific
requests to make it work on OpenVMS, then maybe consider OpenVMS.
Anyway I find it hard to imagine OpenVMS doesn't have something rather
PID-like, and likely there's even a POSIX-compliant get PID call supported
just to make porting C programs easier. After all, they'd know that a lot
of functionality is being coded for other systems, much of it C code that
assumes POSIX and needs little more than that to make it work there too, so
there's a big upside and little downside to supporting common POSIX calls
when developing an OpenAnything.
>>>> 2. How would you develop an OS without the concept of a PID? (No, the sucky
>>>> iPhone "OS" doesn't count, since it DOESN'T MULTITASK.
)
>>>
>>> Well - iOS is an OS.
>>>
>>> It is possible to develop an OS without PID's.
>>>
>>> DOS did not have PID's.
>>
>> DOS also lacked multitasking.
>>
>> And lacking multitasking makes the issue of multiple concurrent instances
>> of a single program rather moot, wouldn't you say?
>
> Yes.
>
> But we are discussing PID.
In the context of controlling concurrent instance count.
>>>> 3. Does anyone tend to make OSen (iPhone "OS" again does not count) that
>>>> *aren't* fairly POSIXy anymore?
>>>
>>> There are not that much point in not counting iOS.
>>
>> See above.
>>
>>> iOS is POSIXy!
>>
>> That, if true, just works in my argument's favor.
>
> Specifically yes.
>
> Generally it confirms that you state information as fact when it is not.
OK, now you've devolved into more or less explicitly calling me a liar, to
my face and in a public venue. That's crossing a line.
Rest deleted unread.
--
Hexapodia is the key insight.