Live data from Hacker News

The Atari 1200XL fiasco

goto10retro.com

41–50 of 88 posts

Re: The Atari 1200XL fiasco

#42
post #33

Earlier quoted context omitted.

BBSes 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 compuserv…

It'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.

I forgot about fidonet, yes that was an option. A few others on that line existed as well.

Re: The Atari 1200XL fiasco

#43
I 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.

Re: The Atari 1200XL fiasco

#44
my 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.

Re: The Atari 1200XL fiasco

#45
post #13
post #5

Earlier quoted context omitted.

The 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.

It’s a bit like an early GPU.

Very much. It was a direct ancestor of the Amiga graphics architecture, and certainly inspired many other less known architectures.

Re: The Atari 1200XL fiasco

#46
post #8

Earlier quoted context omitted.

As 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 fea…

FWIW 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 ht…

Yes, 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.

Re: The Atari 1200XL fiasco

#47
Ali 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.

Re: The Atari 1200XL fiasco

#48

Earlier quoted context omitted.

The 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 interes…

> For their time they were very comparable We can say that now, but it's worth remembering the Atari 8 bit computers came out over two years before the C64. Not such a big gap in computing today, but back then it was a lot. ex-Atari people talking about what they could have done better is always an interesting youtube phenomenon. (as with, for example, ex-Sun people, you hear a lot of theories but you never encounter…

> ex-Atari people talking about what they could have done better

As someone super into retro computing now, who also lived through the history getting my first computer in 1981, participating in users groups, reading all the zines, going to regional and national trade shows for 8-bit home computers, etc, this was (and still is) a significant recurring theme. Owners of 8-bit and 16-bit computers in the 80s/early 90s (and retro hobbyists/collectors today) obsess about the mistakes made by their respective manufacturers. Often this armchair analysis results in frustrated conclusions like "If only (Atari/Commodore/Tandy) had done X" the computer would have "made it" (ie survived against the PC). I engaged in this prevalent pastime myself for years and even today there are forums full of questions seeking to post mortem the "the fatal mistake(s)".

The fascinating part for me is that my early hobby computing led to programming, product-making and tech startup entrepreneurship. By the mid and late 90s I'd evolved from sneaking into Comdex and CES circa 1983 to now launching products in my startup's huge Comdex booth literally next to Microsoft's, with our own private hospitality suites and VIP parties. I'd somehow gone from fanboy to insider. During this era I had multiple private business meetings with industry luminaries I'd idolized including Bill Gates, Steve Jobs, Andy Grove and many others. I'd even met, had a meal with or otherwise gotten to personally know 8-bit era luminaries including Nolan Bushnell, Jay Miner (designer of the Amiga), a couple of Tramiels and so many others. I got to ask my fanboy era questions directly to the players - and the best part was that I was then a peer and the meetings were private. I got a lot more color and perspective than the answers they gave to the press or even at retro-computing conference panels. It was fascinating! But overall I also learned that, aside from a couple notable exceptions, there was no single "Big Mistake". The reality was far more complicated and kind of boring: there were complex business, financial, manufacturing and distribution challenges far beyond users group hobby analysis. The future was unknowable and they were living through the first iteration of what only later became obvious patterns - and they were just doing the best they could to figure it out enough to survive.

By the late 2000s I'd graduated to selling my third startup to a Fortune 500 valley tech giant and became a senior exec driving strategy and identifying new opportunities and markets, as well as leading large teams of MBAs, bankers and lawyers to identify, analyze and negotiate multi-billion dollar acquisitions of other tech companies. And this perspective is the one that most informed my prior obsession with identifying "the fatal mistake" which doomed Atari, Commodore, Tandy, Sinclair and so many others. Having recently retired early, just for fun I've delved into the history and using my post-2000s expertise done rigorous strategic analyses.

In every case the answer is the same and, frankly, a little disappointing: Nothing they could have done would have "saved" them for more than a couple years. While Atari, Commodore, Tandy et al did make many mistakes, none of them were the root cause of their eventual demise. Even if those mistakes had been avoided, it would only have delayed the inevitable. In each case, macro factors beyond their control that were baked into the market, the technology or their own DNA, doomed them. For example, one of the Amiga's greatest advantages in 1985 was the brilliant custom chipset designed to exploit every quirk of analog video timing. And by the early 90s that great advantage was one of its biggest weaknesses. Also, the much-beloved 68000 series processors at the heart of the Amiga and Atari ST were ultimately doomed by the combination of being made by Motorola and being, perhaps, the ultimate expression of CISC architecture (which made them fun to program by hand in assembly language). But RISC was ultimately the only way forward when Moore's Law scaling kept delivering ever more gates into the 90s. But bridging over from CISC to a RISC ISA while maintaining backward compatibility was enormously complex. Only Intel eventually managed it and very nearly died in the attempt. Intel's lead in process fabrication helped them over the hump but Motorola was too far behind in fab tech because they hadn't invested as deeply. For Intel it their lifeblood and, ultimately, existential. For Motorola's board of directors, CPUs were just another business in their portfolio of businesses. Motorola was a decades old conglomerate that made prudent financial calculations. Intel was born as a chip startup and would either live or die as one. Andy Grove had to bet the company and find a way to make it work. Motorola didn't.

Re: The Atari 1200XL fiasco

#49
post #26

Earlier quoted context omitted.

It 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 d…

Indeed, 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 th…

The 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.

Re: The Atari 1200XL fiasco

#50

Earlier quoted context omitted.

> For their time they were very comparable We can say that now, but it's worth remembering the Atari 8 bit computers came out over two years before the C64. Not such a big gap in computing today, but back then it was a lot. ex-Atari people talking about what they could have done better is always an interesting youtube phenomenon. (as with, for example, ex-Sun people, you hear a lot of theories but you never encounter…

> ex-Atari people talking about what they could have done better As someone super into retro computing now, who also lived through the history getting my first computer in 1981, participating in users groups, reading all the zines, going to regional and national trade shows for 8-bit home computers, etc, this was (and still is) a significant recurring theme. Owners of 8-bit and 16-bit computers in the 80s/early 90s (…

This is a good comment. I guess I don't attach the same weight to the CISC/RISC thing you do, but I agree that it's certainly true that the big "the real problem was x" pronouncements are insufficient to explain what really happened. (but are nevertheless quite interesting when they come from the parties involved!)
Post reply on HN