8 ms·
The Atari 1200XL fiasco
- glimshe 2y agoMicrosoft was one of the first companies who fully internalized the importance of seamless backwards compatibility. The lessons had been around for a while, such as the fate of the 1200XL. They would have done a lot better, even at a higher price, if they had focused on it. The Atari 8-bit line had a lot going for it and was arguably superior (flame wars incoming, Atari army please help me) in many ways than the C64.
- userbinator 2y agoMS has unfortunately now fallen greatly from that, and gotten onto the same aggressive and hostile trendchasing practices as the rest of Big Tech. Only their legacy keeps them from totally losing the market at this point.
- pjmlp 2y agoAs someone that bought into WinRT, saw it as .NET 1.0 done right, and went through all the technology reboots between Windows 8 and WinUI 3.0/WinAppSDK, I can only double down on that remark. It was gone so bad that most Windows developers, me included, advise focusing on Win32/Windows Forms/WPF, at BUILD 2024 WPF got back into the spotlight as official Windows GUI framework (WinUI 3.0 keeps being years away from feature parity with UWP, let alone WPF), even Office and XBox teams rather reach out to React Native than bothering to make XAML C++ in WinUI 3.0 work. Check the agenda for BUILD 2025, hardly anything related WinUI 3.0 / WinAppSDK. And if you want to have some fun, come around into the Github discussion issues from all the related repos.
- Mountain_Skies 2y agoIt doesn't seem like Microsoft and Anders Hejlsberg understand what they did when they picked Go over any dotnet language for the Typescript compiler. Anders and his fans insist it was merely picking the right tool for the job but when even the father of C# prefers using Go, combined with Microsoft's tendency to get old technology rot instead of officially cancelling, it sends a very bad message about the future of dotnet. No one wants the shitshow that has been Microsoft's desktop UI over the past decade to spread into the rest of the dotnet ecosystem but most are wary of it happening. Anders was the very last person in the company who should have been the face of the Typescript compiler project using Go. Many have pointed this out but just get shouted down by those haven't had to endure the UI framework pain that the company has put developers through over the past ten to fifteen years. Microsoft officially is completely behind dotnet and is committed to its continued success. Same message they've given for all their UI frameworks. The only difference being dotnet still gets lots of resources but so did all of the frameworks before they were left to rot from resource and leadership starvation.
- pjmlp 2y agoIndeed, it is one of my favourite ecosystems, however I have always been a generalist, I can't get stuck into being a XYZ Developer for too long. As such I get what it means to be in a Microsoft shop, in a UNIX shop, in those that don't care, that use a mix of stacks whatver. The .NET team has made great achievements turning the ship around from Windows only into a cross platform product. However occasionally when they complain on social media, why despite all this effort, there is still some issues getting .NET adoption over Go, Rust, Java, Python, nodejs, you name it, they should start inside Redmond buildings. DevDiv nowadays is no long .NET and C++, regardless of .NET came to be, Microsoft has seen it needs to be back into Java game and even has their own OpenJDK distro. The initial implementation of VSCode support for Go was done by Microsoft, and nowadays they have their own Go distro. While the .NET team makes great developments to ease cloud native development, the projects Azure works on and contributes to CNCF are a mix of Go and Rust for th most part. As for the UI side, from what I can tell, been part of the receiving end, most of the key developers are gone, the new blood are all millennials that grew up with macOS, Linux and Chromebooks, naturally no background experience on Windows developer ecosystem, and strong focus on Web development. Naturally they aren't to blame, they know what they know, what apparently is missing is proper managment, resources and guidance, so that they can deliver to what used to be "Developers, Developers, Developers".
- exceptione 2y agoThe smartest thing Microsoft could do, imho, is cancel all their billion UI variants, bless Avalonia and throw all the saved millions of dollars to them. Then in one instant they get a real cross-platform UI framework, with a competent team as a free bonus. It is actually incredibly compelling, the cross-platform .NET offering. If you look at all the Go, Python and Rust UI toolkits, none hits the bar. They invariably write their own toy framework with 2 components, or they duct tape a leaking C++ toolkit on top with bad interop.
- mixmastamyk 2y agoLinux distros are rewriting their installers and partition tools in web technologies these days. Hard to believe but the direction is clear, no one cares about local UI toolkits.
- neonsunset 2y agoFWIW WinRT / WinUI 3 was ported onto NativeAOT (9). There is are greater ongoing efforts[0] to make the two play nice together from the people working in Windows. But I think it's just efforts from specific individuals who care and the outcome solely relies on their motivation and continued employment, and is not facilitated by the org or its culture in any way, if anything, it happens despite it. [0]: For example https://github.com/dotnet/runtime/issues/114024 https://github.com/dotnet/runtime/issues/114024
- pjmlp 2y agoYes, those individuals have been great contributors and kudos to them, but it is visible, specially from the last community call how things have been going.
- eddie_catflap 2y agoI love the C64 but the Atari 8-bit line was fine indeed (one of my first exposures to home computing was Star Raiders at a family friends house - blew me away). Archer Maclean, author of Dropzone (and other titles) famously labelled them the 'Porsche of home computers'. Where I think the 64 had the edge was in the incredible SID chip and I'd argue the amazing hacks that were found for the system over the years that enhanced what the 64 was capable of. https://en.wikipedia.org/wiki/Dropzone#Development https://en.wikipedia.org/wiki/Dropzone#Development
- rbanffy 2y agoThe big pro of the Ataris was their graphics. Replacing a frame buffer with a display list and a dedicated processor that keeps banging out pixels based on its "program" is brilliant. It's an interesting maximalist counterpoint to the Apple II's minimalist approach to color graphics.
- pavlov 2y agoIt’s a bit like an early GPU.
- rbanffy 2y agoVery much. It was a direct ancestor of the Amiga graphics architecture, and certainly inspired many other less known architectures.
- karmakaze 2y agoThe C64 definitely had better sprites and music, no contest. But there's a certain elegance to the way the Atari did their graphics in particular. It was so much more with simple building blocks where you could immediately see the power of it and take a long time extracting value from it. The SIO of the Atari is also another standout design, which flies under the radar. It enabled a much cheaper diskette drive than the C64. The designer of the SIO, Joe Decuir went on to make USB and credits his work on SIO as the basis of USB[0]. Even the use of letters for devices was already ahead of DOS with D: being for diskette, but that was shorthand for D1:, with D2: being another and any other letter could be an installable device with numbered instances. Keyboard/screen I/O was addressable as E:. [0] https://en.wikipedia.org/wiki/Atari_SIO https://en.wikipedia.org/wiki/Atari_SIO
- ndrake 2y agoAtari 800 XL <3
- atari800xl 2y agoThank you. I love you too.
- sirwhinesalot 2y agoThe Atari line was much better at scrolling, had a much much better master palette, supported display lists (nicer than setting up interrupts in the C64) and the POKEY had some advantages over the SID, not just the extra channel but also in doing beefy sound effects. I don't think any of this is denied by C64 fans. The C64 on the other hand could push nearly 6x the sprite data per line, had Color RAM for more interesting tile work, the SID was more capable for music, and it had much much better support for high resolution graphics. For their time they were very comparable but when (ab)used just right the C64 can do a neat NES impression. The Atari can't do that, but it can do some bonkers 3D using the super low resolution modes.
- curiousObject 2y agoThe 6502-based Atari computers had the CPU clock held at 80% higher than the C64. That must have been a very significant impact at a time when the CPU had to do most of the work.
- RiverCrochet 2y agoIt was. Wasn't the Atari's CPU 1.79MHz (3.58Mhz NTSC clock/3)? The NTSC C64 was close to 1Mhz. But it's worse: The C64's CPU was also slowed down by the VIC-II every 8 scan lines to fetch video data, and slowed down additionally if sprites were enabled. The PAL C64 was actually slightly under 1Mhz but you had a lot more VBlank time to do stuff.
- bluGill 2y agoAtari's CPU was slower in PAL countries, but I don't recall what the speed was. (speed based on something in PAL like the NTSC color clock, but I don't recall what it was called)
- pezezin 2y agoThe colorburst signal? https://en.wikipedia.org/wiki/Colorburst https://en.wikipedia.org/wiki/Colorburst
- JKCalhoun 2y agoI was able to get an Atari 400 (not XL, sadly) for a firesale price. The problem with all the Atari's in my mind was that they were not dev-friendly machines. Commodore machines came with a rather hefty serial bound book that introduced you to programming and gave you a memory map of the hardware, important PEEKs and POKEs. Atari's came with trade secrets.
- mst 2y agoMy first Archimedes came with a ring bound user's manual that was, IIRC, about 1/3 a guide to using the Risc OS GUI, and then 2/3 a programming guide to the version of BBC BASIC that shipped with it. (I remember reading it end to end as a child laid on my parents' bed because the light was better in there than in my room, shortly followed by developing the programming addiction that has stuck with me the rest of my life ;) It didn't cover arm2 assembly, but my parents bought me an extremely good book that did - and described the chip architecture itself in detail as well. I only touched a Commodore at a friend's place to play games on it, but it sounds like they also understood hobbyists :D
- plefebvre 2y agoTrue, the Atari 8-bits did not come with developer docs and in the early years little information was available. This certainly hurt its initial adoption. But starting with De Re Atari by Chris Crawford in 1982, a lot of development material became available. Compute! had a great line of books, including Mapping the Atari. It was shame it took so long for that material to appear because the Atari 8-bit have a rather elegant OS, especially compared to its contemporaries.
- ajross 2y ago> The problem with all the Atari's in my mind was that they were not dev-friendly machines. That was true in the early days of the 400/800, but by 1982 when the 1200XL was released (a few months ahead of the C64) they'd corrected themselves. The board schematics and assembly source for the ROM was a book you could buy at the dealer, and sources like De Re Atari and Compute Magazine had collated all the relevant details of the handful of ASICs such that people could start playing weird tricks. It wasn't Woz's Red Book (neither was Commodores documentation), but it told essentially the whole story of the devices down to the MMIO level.
- ack_complete 2y agoI would say Apple had been doing a fair amount of it prior to Microsoft, if you looked at the way they carefully patched the Monitor II ROM in later models. This is something that Atari didn't get at first when they first revised the OS in the 1200XL and shifted entire sections of code, before reverting major sections back to match the original OS. Problem is, there were always programs that abused the OS so much that it would have been impractical to accommodate them, since bundling extra ROMs is costly. The worst case I know of is a program that used an entire section of the OS ROM as an XOR encryption key for sectors on disk. As for Atari vs. C64, I love the Atari but it needed an update to the custom chips to compete with the C64 and other newer systems. But instead, Atari was looking at adding a 300 baud modem and a speech synthesizer to the computer instead.
- ilamont 2y agoReports of other software incompatibilities due to the ROM changes would start to come out once the 1200XL was actually released and got into user’s hands, hurting its reputation. That wasn’t as big a deal in the 80s as it is now. Reputation was limited to real life friends and maybe a few homegrown newsletters or computer clubs. Very few people were using the Internet to share opinions in the early 1980s, so “reputation“ could be very effectively managed by Atari and other companies through advertising and leaning on trade media to suppress negative reviews and angry letters to the editor. That is, unless the problems were too big to ignore and customer anger became too great, as was the case with many late era Atari 2600 games. A bigger issue for the 1200XL was price as well as something not addressed in the article: competition. By this point there were other platforms to consider, often at better price points with attractive features and software.
- bluGill 2y agoBBSes were a thing back then, and while it wasn't the interest you did have large discussion. If you could afford compuserve (which charged by the minute!) you had a nationwide audience on a platform that was bigger than the internet of the time. A few people also had access to the internet (via their university), or at least usenet (via their work or the internet) and so there was discussion that way - but compuserve was where it was at.
- DrillShopper 2y agoIt'd be interesting to see the FidoNet echomail traffic about the 1200XL as that's likely the most widely available forum accessible to people with a modem since any local BBS could carry it.
- bluGill 2y agoI forgot about fidonet, yes that was an option. A few others on that line existed as well.
- os2warpman 2y ago>That wasn’t as big a deal in the 80s as it is now. It was a big deal for me. Software expenses were a huge portion of the cost of owning a computer. Almost always the price of the computer was less than the cost of buying software to run on the thing. Letter Perfect was around $300. If it didn't run on the 1200XL I'm not shelling out $800 for the computer and another $300 for a compatible word processor. I am convinced that cross-vendor incompatibility was THE reason for CP/M's failure. Not anti-competitive behavior, not shenanigans, but the fact that if you spent $495 on the Kaypro version of Wordstar and then bought an Osborne, it wouldn't work. Same Z80, same CP/M, wouldn't work. Even today PC manufacturers are only starting to remove the BIOS compatibility layers that allow you to boot >30-year-old versions of DOS on a modern hardware, and Apple has provided binary translators since the 1994 PowerPC transition and supported them for years after breaking native compatibility.
- vaxman 2y agoRIP Jay Miner https://youtu.be/mpWe5C58y40 https://youtu.be/mpWe5C58y40
- jfultz 2y agoThe 1200XL was my first computer. My family purchased it at a department store at a fire sale price (IIRC Montgomery Ward's, $199) after Atari stopped manufacturing and began dumping its inventory to make way for the 600XL/800XL. I had been researching a computer to get for ages, but my family was very careful about how we spent money, and it was a big purchase. We had seriously considered getting a TI-99/4A when TI exited the business, but we were concerned that it was just going to be a dead end. But the chance for a cheaper entry into an established ecosystem was great (that and me begging my mother to finally, finally get a computer!). Re compatibility, I never came across software that didn't run on it. I'd read in magazines that there were issues, but never once experienced it. One interesting software change, though (but true of other XL computers, too) was that the color "artifacting" worked differently on it than it did the 400/800. For example, Ultima III used color artifacting, and so playing it on my system produced some incorrect colors...most notably the sea was red. I did come across one hardware issue...a cheap third-party parallel interface adapter that didn't work, and that we thought at the time was defective, but I now think it's likely to have been affected by the incorrect power wiring in the 1200XL's SIO adapter. It was cheap enough that we didn't lose too much money on it, and I ended up getting the far superior ICD P:R: Connection instead. The Atari community was a super great community to be in. And in so many ways, Atari was doing things that wouldn't be seen again for years, if not decades. Atari's SIO port is famously a predecessor/inspiration of USB. The APX Exchange was basically a third-party app store decades before Apple popularized the concept. The machine was hackable and moddable (I bought a 256KB upgrade kit for mine). When I migrated to PC for college use, it hurt to have to fall back to CGA...even EGA was just ugly, compared to what my 1200XL was capable of (although the 80 column displays were nice compared to Atari's 40-column).
- sokoloff 2y agoMy first owned computer was a 1200XL as well. Found a game that read raw keystrokes and that was different from the 400/800 to the 1200XL. I patched my copy of the game and sent the patch to the publisher (Microprose, IIRC) but never heard from them.
- varelse 2y ago[dead]
- runjake 2y agoI had an 800XL and a 520ST, but I don't recall ever seeing or hearing about the 1200XL. I feel like I just entered some bizarro universe. But wow, I really love it's physical design.
- forinti 2y agoThere was an Apple II clone in Brazil that used the same design. It was called TK2000. I never found out why they copied the design of a completely different machine. I guess they just liked it.
- runjake 2y agoVery neat! Apparently didn't have the top row of function buttons. For those reading: https://en.wikipedia.org/wiki/TK_2000 https://en.wikipedia.org/wiki/TK_2000
- cmrdporcupine 2y agoI bet they got their hands on the old 1200XL moulds somehow. Huge expense to make those.
- bentt 2y agomy best friend’s parents bought this and kept it in their bedroom for some reason. They allowed us to play with it, but it had no storage they didn’t buy anything to go with it. So we would just type programs in from magazines and the worst part about it was that sometimes we wouldn’t finish and then his parents would shut the computer off at night and we’d have to start over.
- alamortsubite 2y agoAli Baba and the 40 Thieves and Atari Basketball are two additional games that made use of the 400/800's extra joystick ports. Ali Baba was turn-based, IIRC, so not as exciting of a use case, but playing basketball with three other kids simultaneously was a riot. Very special for the time.
- SeenNotHeard 2y agoAtari's port of Asteroids also supported four joysticks. You could play melee, co-op, or team mode, with four players on the screen at once. It was a blast. https://www.atarimania.com/8bit/files/Asteroids_manual.pdf https://www.atarimania.com/8bit/files/Asteroids_manual.pdf
- Swordquest 2y agoI wrote a four player "Tron lightbikes" game that used all four joysticks. But I was just a kid and didn't really know what I was doing, so there was no collision detection - people being out because they ran into a wall was based on the honor system. lol.
- glonq 2y agoI jumped from an 8-bit Atari to a CGA PC/XT clone and it was surprising how much forward I jumped in power and capability and storage, yet how much -backwards- I jumped in graphics and sound. Those were great lil' machines and even got me online (to BBS's at 300baud) back in the day.