Live data from Hacker News

Halt and Catch Fire

unstack.io

71–80 of 117 posts

Re: Halt and Catch Fire

#71
post #22

Earlier quoted context omitted.

Yeah a truly fantastic show all the way through the end. One of my favorites by far.

I have to admit, when a specific person died I was feeling so bad about it I never watched the last episode. I still have it on the drive how many years later.

That’s too bad because I think the last episode is brilliant. I think about it a lot even years after seeing it.

Re: Halt and Catch Fire

#72
post #7
post #3

It was a fun show. I really enjoyed it, a fictional run through the 80s and 90s computing industries.

It's a shame that it is such a niche show in practice. The acting of Lee Pace and Mackenzie Davis in particular are so good across all 4 seasons. I recommend it at every chance I get, but few people ever watch it. They're more likely to give Silicon Valley a try.

I sometimes tell people that HCF is why I wanted to become a programmer and Silicon Valley is why I didn't become one.

(I watched both of them years after I decided not to go into industry.)

Re: Halt and Catch Fire

#73
post #10

There's such an annoying scene in the first episode of that show that kinda broke the immersion for me. They introduced Cameron Howe as some sort of world class hacker that could do anything so one of her first scenes was her typing something.. and typing she did, one finger at a time. I mean, wtf. World class hacker that literally types one finger at a time, like she had never used a keyboard before. That scene near…

My father is a journalist and learned to type by himself on typewriters using his index fingers. He writes a lot and he is really fast. I don't have any issues with that.

Re: Halt and Catch Fire

#74

The Commodore PET 4032 video system was generated by a 6545 (6845 equivalent) cathode ray tube controller, which generated the video buffer addresses and the HS and VS sync pulses. This was memory mapped and if one was not careful with POKE commands, you could effectively stop the CRT raster scan, leaving the beam parked at the center of the screen. This could burn the phosphors off that spot in a matter of minutes.…

That was definitely a defect of the monitor, not a serious mistake of the programmer. Any damaged monitor should have been paid by whoever had approved such a monitor design, even in the case of a monitor integrated in an all-in-one computer, which was not supposed to be disconnected from the computer.

I have also seen some monitors designed so badly, like the IBM MDA monitor mentioned at the link provided by userbinator, but all the TV sets that I have ever seen could only be synchronized to the desired scanning frequencies by the "sync" pulses, but they would oscillate freely in the absence of sync pulses.

The cost savings by not having relaxation oscillators or PLLs that would drive the raster scan in the absence of sync pulses, and which would limit the range of acceptable scan frequencies to safe values, have always been negligible, even by the time of the vacuum tube TV sets, and much more so by the time of computer monitors. The elimination of physical safety devices is not an acceptable way to reduce costs, especially when the savings are so small as in this case.

Re: Halt and Catch Fire

#75
post #60

This show captures much of what I miss about computing in the 80s and 90s. You could get your hands on hardware, be able to largely understand what all the hardware and software was doing. You mostly used computers as tools, which only accepted commands and didn't try to affect your decisions or workflow (yes, there was Clippy). The leaps forward in computing power, memory and storage were more impactful to the every…

One thing i found very interesting over the years is that when people seem to abuse systems ( key activation, share netflix accounts, vpn, torrents) it’s considered a serious crime, but when companies openly abuse systems ( unsubscribe maze, addiction, fraud ) it’s frowned upon.

That should be the other way around. Until then systems will always try to rule over people and people will adapt for better or for worse.

Re: Halt and Catch Fire

#76
I had an old projector; If the film roll stopped for any reason (operator error, getting stuck, etc...), the lamp was so bright that it'd catch fire.

Re: Halt and Catch Fire

#77
post #60

This show captures much of what I miss about computing in the 80s and 90s. You could get your hands on hardware, be able to largely understand what all the hardware and software was doing. You mostly used computers as tools, which only accepted commands and didn't try to affect your decisions or workflow (yes, there was Clippy). The leaps forward in computing power, memory and storage were more impactful to the every…

Computers still do the exact same thing they did back then, which is to read opcodes and do binary math. That is all. It is people and corporations that found a way to monetize them which is hostile to us users. But I think that with time, this too shall pass and computers will still do what they always did. You can still enjoy designing a small PCB, working with microcontrollers and building something fun.

Re: Halt and Catch Fire

#78
One cool thing about this is that there are places where old compilers feared to tread, on the 6502 for example any opcode (apart from $A2, LDX #imm) ending in 2 would be a JAM instruction - CPU just stops. The later CMOS versions still did that for most of the $x2 instructions but some were converted to NOP.

So if you're implementing a 6502 in an FPGA, and you want to add (say) stack-relative addressing, there's a nice set of opcodes that you know won't ever be in conflict with the usual ones, because any 6502 ever issuing it would immediately halt (but not catch fire).

Re: Halt and Catch Fire

#79
post #10

There's such an annoying scene in the first episode of that show that kinda broke the immersion for me. They introduced Cameron Howe as some sort of world class hacker that could do anything so one of her first scenes was her typing something.. and typing she did, one finger at a time. I mean, wtf. World class hacker that literally types one finger at a time, like she had never used a keyboard before. That scene near…

The only reason I learned to touch type was out of boredom and the fact that the only “game” for the TI99/4a system (it had an “extender” with floppy drive and ran some spreadsheet) that my dad brought home from work at weekends was a touch typing tutor. When I started CS, I was in the tiny minority in my class that could touch type. During an introductory lecture for the course, one of the tips was “learn to touch type”.

Re: Halt and Catch Fire

#80

The Commodore PET 4032 video system was generated by a 6545 (6845 equivalent) cathode ray tube controller, which generated the video buffer addresses and the HS and VS sync pulses. This was memory mapped and if one was not careful with POKE commands, you could effectively stop the CRT raster scan, leaving the beam parked at the center of the screen. This could burn the phosphors off that spot in a matter of minutes.…

That was definitely a defect of the monitor, not a serious mistake of the programmer. Any damaged monitor should have been paid by whoever had approved such a monitor design, even in the case of a monitor integrated in an all-in-one computer, which was not supposed to be disconnected from the computer. I have also seen some monitors designed so badly, like the IBM MDA monitor mentioned at the link provided by userbin…

[deleted]
Post reply on HN