Have you seen the insane complexity of modern CPUs? Ain't no one hand coding that like a 6502 in 1985.
I wonder if there's anyone alive right now who would be capable of such a task.
If the hardware was fixed, I don't see why not.
Might not be as fast as the optimisations compilers do these days though.
If you have to support thousands of types of GPU and CPU and everything else, then fuck no.
Even if one did, say using x86, it would still just be interpreted by the CPU into the CPU's native opcodes, as the legacy instruction sets are interpreted/translated.
as the legacy instruction sets are interpreted/translated.
Wth? That's it, I'm sticking to the AVR then
Hello everyone and welcome to another video.
The YouTube algorithm works in mysterious ways.
Because I'm nice, to anyone who doesn't get the reference: https://www.youtube.com/@MarcelVos
Rollercoaster Tycoon was the last of an era, not a sudden burst of genius.
Before Doom (1993), almost all games were assembly. Doom was a shock to the industry. You could now write a high performance, multiplatform, sophisticated game in a compiled language (C). When I say multiplatform, I don't just mean how it was ported to everything later. It was developed on NextStations first. DOS was the first port. So it proved all of the above immediately on release.
We take for granted that C is performant now, but that wasn't obvious until optimizing compilers got good and someone tried.
Rollercoaster Tycoon (1999) is the last notable title that used ASM. It's impressive in many ways, but it wasn't as much of a standout as it seems now. Six years earlier to its release, that was just how games were done.
It's notable that the only port of Rollercoaster Tycoon was the original Xbox, which was also x86. Nobody wants to rewrite it for anything else.
Before Doom (1993), almost all games were assembly.
Carmack wrote Wolfenstein 3d in C. Star Control and Dune 2 were C.
> almost
I used those as examples but I claim that most everything was C by the early 90's. The statement that C compilers got fast which allowed it isn't true. When a new compiler came out it was always a couple of percentage points faster than the old version. Meanwhile hardware was doubling in performance every two years.
C compilers didn't need much optimization because there wasn't much performance that could be optimized into code on the simple CPUs of 1992 when Doom was being written. CPU's weren't the superscalar multi core monsters they are today. A compiler couldn't take advantage of reordering instructions to use multiple adders because there was only one.
Those games didn't have the splash that Doom did for this sort of thing.
https://web.archive.org/web/20010105180900/http://www.gamespy.com/legacy/articles/devweek_c.shtm
Mainstream application programmers switched to C in the early 80's. Game developers were slower to switch, because their small teams and focus on performance kept assembly language viable till the following decade. When id Software released DOOM, they surprised much of the industry by having no reliance on assembly code--despite excellent game performance, and by successfully cross-developing the game (in NeXTstep and DOS), then successfully porting it to an astounding variety of platforms.
Those games didn’t have the splash that Doom did for this sort of thing.
I would say that Wolf3d would certainly count as proof of concept.
Eventually it sort-of got a rewrite to create RollerCoaster Tycoon Classic, initially for iOS and Android, later for Windows, macOS, and Nintendo Switch. It largely is a rewrite of RollerCoaster Tycoon 2, with the goal of bringing the game to more modern platforms, and the save files for parks and rides are compatible. In this interview with Atari Club, Sawyer says the rewrite was in C++ but even with a team of people still took longer to write in C++ than it took him to write the original in x86 assembly.
If anyone previously paid attention to RCT Classic, it’s been seeing some development work again and is working on Android again. They also made RCT Classic+ on Apple Arcade (basically just the game and all the expansions included) and also updated the regular versions of RCT Classic so they run correctly again (RCT Classic stopped working on macOS when Apple dropped support for 32-bit applications and Atari didn’t release a recompiled game until recently).
Just to throw on more factoids:
Wasn't Gabe Newell either the first, or among the first, to port Doom to Win 95?
He was an analyst at Microsoft who was tasked with finding out how many computers ran Windows to determine market share. Part of the question involved asking what other software was installed and the only software used more than Windows was Doom. This made GabeN realize the market potential of games and he left Microsoft shortly afterward.
See, I've heard that story, that he basically ran ... well, arguably, a worm that did network analysis on what was installed on every computer in the MSFT internal network, realized more people had DOOM installed... than Windows...
... and I have also heard that he actually ported DOOM to... either MS DOS, or Win95... ?
I genuienly do not know which is true, if they're all true, if they're all false... I can't remember the source for each of these, but I know I've heard or read all these semi-close variants from somewhere, over the years.
Just saw this article recently. Gabe was part of a team trying to convince developers that they would be better off writing their games with more abstracted code/libraries instead of writing their own interfaces (some of which were written by people convinced they were being really efficient but were actually terrible). One thing they did to prove their point was going to id and offering to have Microsoft port Doom to Windows for free. But the experience and seeing the success id was having distributing their own game led Gabe to launch Valve.
Before Doom (1993), almost all games were assembly
No? Not even close? Why is it people get away with saying such stupid things on the internet?
Because it's true. Here's an article from Tim Sweeney from 2001:
https://web.archive.org/web/20010105180900/http://www.gamespy.com/legacy/articles/devweek_c.shtm
Mainstream application programmers switched to C in the early 80's. Game developers were slower to switch, because their small teams and focus on performance kept assembly language viable till the following decade. When id Software released DOOM, they surprised much of the industry by having no reliance on assembly code--despite excellent game performance, and by successfully cross-developing the game (in NeXTstep and DOS), then successfully porting it to an astounding variety of platforms.
having no reliance on assembly code
That's not true. The original Doom has assembly. They replaced it for the Linux source release. But by that time PC hardware was much faster ( remember back in the 90's performance doubled every 2 years) so it wasn't needed.
"Planar.asm"
Focus on performance, wow, well the industry has certainly changed a bit.
Performance is very much still a significant factor. At the end of the day, games are expected to run at certain FPS on certain machines. The machines have gotten better to the extent that unoptimized code can be used sometimes, but when competing for graphics, badly optimized games will have to sacrifice fidelity to hit performance targets, where well-optimized games can get squeeze out better graphics and hit those same targets.
There's plenty of tricks these days but optimized code will always have an edge.
is there a NPM package for assembly? I need to keep access to right pad my strings package.
Here's a neat video about the creator and the game - https://www.youtube.com/watch?v=0JouTsMQsEA
I will never not upvote an Ahoy video. The guy is a legend in video game documentaries. Check out his Monkey Island video as a follow-up
Another really good one that I've watched at least 4 times is his Polybius video. He's an incredible documentarian and an equally great researcher.
I'm sure some of the Polybius one was dramatized a little (apart from what was clearly labeled as actors reading the transcripts), but it makes for an unforgettable watch. And the music!!
Dude got millions for it. Well deserved imho.
And most startlingly: no git
Edit: y'all're right, version control is for wimps. What's life without some adrenaline?
Who needs git when you have a B: drive and a Save As command for tycoon43.asm
Version control? You mean this?
./src
./src_1998_11_05_added_people_swimming
./src_1998_11_06_added_death_mechanics
./src_1998_11_06_0_removed_swimming_lol
Did the developer use any version control though? SCCS has been around since the early 70s, RCS and CVS since the 80s. The tools definitely existed.
Also, it was a single dev, which makes SCM significantly simpler!
In my experience (some games in z80 and 68000 in the early 90s), version control wasn't considered until mid-90s sometime, and at first wasn't trusted. There were network backups, but I don't know if they had revisions.
Merging seemed like it couldn't possibly work well, so we would try to have separate ownership of different files. Although there would be only a handful of programmers on a team, so that was easy.
Prior to that, backup and versioning was manually handing a floppy or two to someone each week.
Epic Pinball was another game that I recall was written in assembly. When your old 286 struggled to run games at a decent framerate, Epic Pinball would run in a smooth 75fps or whatever you set your CRT monitor to.
Epic Pinball, if I recall correctly, also used some ModeX trickery, meaning it had most of the pinball table in VRAM, and then modified the VGA framebuffer pointer for scrolling, then only moving as much data as it was needed (ball, flippers, etc)
"Try writing it it in assembly"
I want to get off Mr. Bones' Wild Ride.
Chris Sawyer is an absolute legend
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.