Re:America’s Cities Are Running on Software from the ’80s
by jacobush on Thursday February 28, 2019 @11:42AM
(#19272643)
The Toyota computer is like a super computer compared to old mainframes. IIRC the Toyota program had 10k global variables updated by spaghetti C code. So you had a lot of space, enough to shoot yourself with C code. Old mainframe code in contrast often operated on records in a batch fashion, with a pretty clear input and output.
Of course, the antipattern on enterprise code comparable to thousands of global variables in C code, is to have thousands of columns in hundreds, or thousands even, of database tables, all intertwined and used only God knows where.
Re:America’s Cities Are Running on Software from the ’80s
by monocasa on Thursday February 28, 2019 @04:57PM
(#19275656)
AFAIR, the were also autogenning code from a Matlab model of the engine, and that's where the 10k globals thing is from. Like yeah there's technically C code that's doing that, but come on.
Re:America’s Cities Are Running on Software from the ’80s
by freedomben on Thursday February 28, 2019 @12:45PM
(#19273266)
Interesting, I thought the "unintended acceleration" was actually just floor mats creeping up and holding the accelerator pedal. Gonna have to google some stuff now :-)
Re:America’s Cities Are Running on Software from the ’80s
by pjc50 on Thursday February 28, 2019 @02:19PM
(#19274216)
https://news.ycombinator.com/item?id=9643204
It's one of those Rashomon situations where I'm not sure we can ever be entirely sure but it seems to have stopped.
Re:America’s Cities Are Running on Software from the ’80s
by jackalo on Thursday February 28, 2019 @04:56PM
(#19275636)
Thank you for linking that. The comments in it share some terrifying stories.
Re:America’s Cities Are Running on Software from the ’80s
by ambicapter on Thursday February 28, 2019 @02:38PM
(#19274349)
That was Toyota's explanation for what was happening. Turned out to be a lie or a hasty conclusion, I don't remember which.
The only thing that resource constraint forces is less code, especially less dependencies, because you run out of space.
The Toyota "unintended acceleration" court case was a flagship example of bad embedded code, that we rarely get to see.