4 ms·
Was this not already understood by the 1980s? At least in IBM? Hence why mainframes are so expensive and why almost every big bank still pays those megabucks. I
by MichaelZuo 5y ago
Was this not already understood by the 1980s? At least in IBM? Hence why mainframes are so expensive and why almost every big bank still pays those megabucks. In an industry where a single error at just the wrong place could destroy a multi trillion dollar organization overnight, people are usually more perceptive of even the remotest possibilities.
- michael1999 5y agoThe entire cloud movement is recapitulating the development of the mainframe: containers, io budgets, metered usage, etc. Our industry has the memory of a bright dog.
- imtringued 5y agoWhat's wrong with adopting a model that works? It's not like IBM was trying to make it accessible in the first place.
- michael1999 5y agoMy complaint is that we ignored these lessons for 40 years, not that we are finally beginning to take them seriously now.
- detaro 5y agoSo because it's similar to something we had in the past it's supposed to be a bad thing? Or the fact that people did something else in between is supposed to be a bad thing? (Also, obviously many people in the industry know about mainframes, memory is not the issue)
- michael1999 5y agoThat we let Intel turn ecc into a premium feature to support market segmentation for a generation, and completely ignored data integrity in our storage systems while disk capacities reached terabytes was definitely a bad thing, and that’s on us as an industry.