OP’s point exactly - it seemed somehow in their vibecoding workflow, they forgot to even do a human architectural sniff test for the stuff everyone knows. It reflects very negatively on them.
4,326 karma · joined August 4, 2023
OP’s point exactly - it seemed somehow in their vibecoding workflow, they forgot to even do a human architectural sniff test for the stuff everyone knows. It reflects very negatively on them.
Now you’re thinking like a Big Blue sales rep.
PS – Primary sources for the IBM 7950/HARVEST on Bitsavers, excellent as always:
And the rest of the world is envious!
EDIT: d’oh, of course it’s so that they can sell more Linux LPARs.
It looks like I wrote that in a confusing way! My intention was to ask about what features of the engineering discipline was motivating OP's comparison. Maybe a better series of comparisons would have been...
- the 747 – program conception in '63, delivery in '69; – the A350 - first sales in '05, delivery in '13;
which I think captures the slow pace, and large dependency chain, of any significant program beyond a revision.
Would that be more like other engineering fields? An interesting comparison would be aerospace, for example – it took 15 years to build the first A380, and tens of thousands of indispensable technical niches.
I think the last one was seeing a skilled electronics repairman do surgery on a CT machine controller.
I recommend taking the time to go to the original writeup -- you can see all the soldering on perfboard!
(More seriously, it's incredibly informative if your understanding of homebrew busses is stil in the "shared CPU bus" era. The interface to 68k memory-mapped IO is described in the "First PCI tests" section.
The key resulting limitation right now is that bus mastering is not implemented, but I don't think this is inherently impossible on the 68k bus: Macintosh addon SCSI cards did the same thing, no?)