News for hackers. Stuff that matters.
Re:OpenAI's employees were given two explanations for why Sa... by jeremyjh on Monday November 20, 2023 @09:51PM (#38358394)
They would have just forked the code and maybe merged some changes back and forth, no real need for cross-platform code.
Re:OpenAI's employees were given two explanations for why Sa... by primax on Monday November 20, 2023 @10:01PM (#38358478)
This was pre-1983. Forking wasn't a thing at the time. Any kind of code management was cutting edge, and cross-platform shared code wasn't even dreamed of yet.
Re:OpenAI's employees were given two explanations for why Sa... by bawolff on Monday November 20, 2023 @10:19PM (#38358647)
Forking and merging is a social phenomenom. Sure git makes it easier, but nothing stopping anyone from just copying and pasting as appropriate. Not to mention diff(1) was invented in 1974, and diff3(1) in 1979, so there were already tools to help with this, even if not as well developed as modern tools.

I'm also pretty sure cross-platform code was a thing in 1983. Maybe not to the same extent and ease as now, but still a thing.

Re:OpenAI's employees were given two explanations for why Sa... by WalterBright on Monday November 20, 2023 @11:38PM (#38359323)
Successful 8086 projects were usually written in assembler - no way to get the speed and size down otherwise. I'm pretty sure Lotus 123 was all in assembler.
Re:OpenAI's employees were given two explanations for why Sa... by bawolff on Tuesday November 21, 2023 @12:19AM (#38359653)
I'm not an assembly programmer and not very familiar with how that world works, but even then, if the two OSs were for the same architecture (x86), couldn't you still have a cross OS main part and then specific parts that deal with operating system things? I normally think of compiled languages like c being an abstraction over cpu architecture, not operating system api.
Re:OpenAI's employees were given two explanations for why Sa... by WalterBright on Tuesday November 21, 2023 @12:46AM (#38359847)
Yes, you can have common assembler code among platforms, provided they use the same CPU.

From what I've seen of code developed in the 80s, however, asm code was not written to be divided into general and os specific parts. Writing cross-platform code is a skill that gets learned over time, usually the hard way.

Re:OpenAI's employees were given two explanations for why Sa... by jeremyjh on Monday November 20, 2023 @10:40PM (#38358818)
You make a copy of the files and work on them and that is a fork.
Re:OpenAI's employees were given two explanations for why Sa... by adastra22 on Monday November 20, 2023 @11:06PM (#38359043)
How do you merge changes between the source trees?

Keep in mind this predates basically ANY kind of source control. It would have been nearly 3x the work.

Re:OpenAI's employees were given two explanations for why Sa... by dragonwriter on Monday November 20, 2023 @11:48PM (#38359391)
> Keep in mind this predates basically ANY kind of source control.

It might be before they were ported to DOS or OS/2, but it definitely wasn't before source control existed (SCCS and RCS were both definitely earlier.)

Re:OpenAI's employees were given two explanations for why Sa... by adastra22 on Tuesday November 21, 2023 @12:18AM (#38359646)
OK: Keep in mind this predates basically ANY kind of source control in common usage in software engineering.
Re:OpenAI's employees were given two explanations for why Sa... by bawolff on Tuesday November 21, 2023 @12:23AM (#38359695)
3x the work may still fall under reasonable cost.

If architectured properly (big if) you can split up the project appropriately so there is a common core and individual parts for specific OS.

Is it extra effort? Sure. Impossible? Definitely not.

Re:OpenAI's employees were given two explanations for why Sa... by WalterBright on Tuesday November 21, 2023 @03:37AM (#38361011)
I've also successfully converted some rather large x86 assembler programs into C, so they could be ported to other platforms. It's quite doable by one person.

(Nobody else wanted the job, but I thought it was fun.)

Re:OpenAI's employees were given two explanations for why Sa... by gruturo on Tuesday November 21, 2023 @06:27AM (#38362229)
Uh? Quite wrong.

SCCS was created in 1973. We're talking about over a decade later.

Also primitive forking, diffing and merging could be (painfully) done even with crude tools, which did exist.

Re:OpenAI's employees were given two explanations for why Sa... by adastra22 on Tuesday November 21, 2023 @02:57PM (#38369170)
These were not in common usage in the software industry.
Re:OpenAI's employees were given two explanations for why Sa... by Dylan16807 on Monday November 20, 2023 @10:15PM (#38358606)
Fork just means two groups start with the same code and work independently.

It was a thing.

Re:OpenAI's employees were given two explanations for why Sa... by jrflowers on Monday November 20, 2023 @10:44PM (#38358856)
Should’ve just made it an Electron app
Re:OpenAI's employees were given two explanations for why Sa... by DonHopkins on Monday November 20, 2023 @10:54PM (#38358945)
You'd need a Beowulf Cluster of Apple //e's to run an Electron app in 1983!
Re:OpenAI's employees were given two explanations for why Sa... by jrflowers on Monday November 20, 2023 @11:00PM (#38358989)
They could have charged a subscription for their cloud based offering then
Re:OpenAI's employees were given two explanations for why Sa... by adastra22 on Monday November 20, 2023 @11:04PM (#38359029)
Been a long time since I heard "Beowulf Cluster"!
Re:OpenAI's employees were given two explanations for why Sa... by inDigiNeous on Tuesday November 21, 2023 @08:49AM (#38363551)
Had to log in just to upvote this comment, brought back nostalgia from the Slashdot days of yore.
Re:OpenAI's employees were given two explanations for why Sa... by saalweachter on Tuesday November 21, 2023 @10:14AM (#38364714)
Eh, C of this era, you're definitely talking some sort of #ifdef PLATFORM solution.