Hacker News new | past | comments | ask | show | jobs | submit | emersonrsantos's comments login

Old components are still (and will be) manufactured, since so many old tech depends on it, like refrigerators, air conditioners, washing machines, microwave ovens, ...


Some old components will be, sure, but there are some chips that aren't manufactured anymore. There's no one blanket rule.


I doubt it would be impossible to replace a Pentium 2 machine in most of the western world for at least the next 20 years.


I worked at a company that decided to do a new design because the chips for the old one had been out of production for decades and a solid percentage of what was still available on eBay was sitting in the warehouse to be scavenged for new production.


Pentium 2s aren't the only retro computers out there. There's many different computers, especially in the 1980s, that have components that are just simply not made anymore -- break one of those components, and you'll have a hard time repairing / replacing them.


That's true, but in many cases, it's not the integrated circuits (ICs) that fail, because they tend to be quite reliable. It's more often the capacitors, resistors, storage devices and power supply components that degrade over time. Capacitors, in particular, can fail due to heat, aging, or voltage surges, which can lead to failure in devices even if the ICs are still in good condition. Power sources can also fail due to wear on these exact components.


I've seen enough electronics repair videos that it seems the default for troubleshooting absent other conspicuous damage is to start checking the electrolytic capacitors.

https://en.wikipedia.org/wiki/Capacitor_plague


There was a time when Gigabyte started selling more robust motherboards with quality capacitors that would last much longer. After seeing so many old motherboards dying from blown capacitors I was very happy to get one. Those motherboards so far held the full length of their meaningfull life until the CPU just got too slow to use for anything. Still try to look for that type of capacitors when I build new stuff for friends and family.

The Gigabyte line is called "Ultra Durable" and have solid capacitors instead of the electrolyte ones.


> It's more often the capacitors

And the electrolyte can and will start to leak and foul the ICs around them, if not by ruining the traces/pads, then they can also foul the legs and/or find their way into the chip package itself, so the ICs will fail as a secondary issue.


So better to turn it on sometimes, without power cycling so much, to keep the electrolyte fluids wet, to extend the equipment life. Let it rot and dry and it will.


That's not how it works.

Electrolytics which have not had voltage applied in a long time (decades) may need gradual reforming, but if they aren't hermetically sealed they will dry out no matter what --- and heat will accelerate that process.


I miss this from the Internet early times. The Church of the SubGenius, IOCCC, Phrack Magazine, The Tao of Programming, ...


I think POC||GTFO carries on some of the spirit of those times.


GTFO yes !



Ice age


IBM ISPF suite is gorgeous.


The whole IBM 3270/5250 family is interesting evolutionary line in the sense that it is completely separate from the VT100 style UNIX terminals.


Happy to onboard a startup like this and have them spend thousands of $ on me just on consulting on how to migrate to AWS/GCP/Azure without downtime.


Which they might have now that they have a running business...


A nicer problem to have.



We tried that in the company I worked, project was abandoned 1 year later. Improvements and better practices were incorportated into the old codebase which is still scaling today.


This makes me wonder if the system was still capable of supporting improvements, better practices, and increased scale, why was it targeted for a rewrite in a first place?


Anything that supports Markdown. I use just a repository hosted on GitHub that has a history and that I can access anywhere.

If you need privacy, just use git-crypt.


Good advice. I thought about making a private repo for this. Nothing that I need to encrypt, really, just notes for things I find online.


Does the author ever heard about using loops in Ansible? with_dict can save you around 20-30 lines of code.


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

Search: