Hacker News new | past | comments | ask | show | jobs | submit login

Yeah it was over 30 years ago. I’m sure with more experience it might have been easier conceptually. I didn’t have any trouble with COBOL but found the whole mainframe environment to be rigid, crusty, and difficult to understand and use compared to the Unix systems I had used in school.



I don't understand the need for "mainframes" in industries such as banking. Isn't a mainframe just a beefy server?

I get that 40 years ago it made sense for a bank processing thousands of transactions per day to have a big computer to do that.

But today that could be done on a laptop with a Python script. Has the compute needs really grown proportional to the speedup of the hardware?


Weeeellll... yes and no. You aren't wrong, but I would just note that mainframes were remarkably reliable. They pushed a lot of boundaries on things that we still kinda struggle with today in terms of data integrity, redundancy, hot-swapability, recovery, etc. No question that today's systems are faster and perhaps in some ways more affordable. Definitely the case that the average person wanting to learn about software has more resources and tools available that once upon a time required access to these multi-million dollar machines. But, there's definitely tradeoffs between those centralized systems and our distributed systems of today.


No they are not just beefy servers. Their raw processing power is not remarkable. They are built for throughput. I/O and peripherals are handled by separate hardware so the CPU only deals with data in memory. They also have more sophisticated virtualization and scalability features than standard servers or PCs.

https://en.m.wikipedia.org/wiki/Mainframe_computer




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

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

Search: