Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Puts your migration projects to shame.


Yep... days worth of work to get Python code I wrote 3 years ago working again from all of the 'bitrot.' Can't imagine how much work it must be for them to produce new binaries to update these old systems from modern computer hardware.

Although I suppose it could actually be easier depending on how the code works- perhaps it's just simple bare metal assembly without the approx 10^99999 libraries a modern python stack has.


It's probably a lot easier in a way, because they don't have to worry about external dependencies changing at all. Modern code is a real PITA that way.

What's hard about their work is 1) it's really, really slow to communicate with, so you can't iterate quickly, 2) the tech is really old and unlike today's stuff, so it's very specialized domain knowledge.


Also whatever you do don't break the receiver pathway! Otherwise you will need to send a technician on-site.


The lead engineer from the 70's is actually in Voyager 1's fuselage. It's cramped but they seem to be doing ok! They're just taking pictures with an old Canon point and shoot.


/api/v1 stands for Voyager 1 and is forever.


Having no customers does help a lot.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: