News for hackers. Stuff that matters.
Re:fs.promises.readFile is 40% slower than fs.readFile by boring_twenties on Wednesday March 03, 2021 @09:55PM (#26338054)
Sounds funny, but is it actually unreasonable?

Presumably, the RAM was a rounding error in the total budget.

And this move eliminated an entire class of bugs (use after free).

edit: And, you don't have to worry about memory fragmentation, or how long free() might take in the worst case.

Re:fs.promises.readFile is 40% slower than fs.readFile by gizmo686 on Wednesday March 03, 2021 @10:21PM (#26338221)
When the European space agency designed the Ariane 4 rocket allocated 16 bits to some variable relating to its horizontal velocity. This variable was only used during the first minute of flight, and engineers computed that it could not possibly overflow given the launch profile Ariane 4 used. Because of this and limited processing power, engineers omitted an overflow check. This worked fine, and Ariane 4 would go on to launch succesfully 113/116 times (97%).

In 1996, Ariane 4's successor, Ariane 5, took its maiden voyage to carry the Cluster constellation into orbit, when this happened https://www.youtube.com/watch?v=gp_D8r-2hwk&t=54s

Ariane 5 used a different launch profile. The impossible was now possible and the 16 bit value overflowed. The inertial reference system failed, along with its backup (which was running the same code), causing the rocket to receive wrong data.

Re:fs.promises.readFile is 40% slower than fs.readFile by stonogo on Wednesday March 03, 2021 @10:26PM (#26338250)
Sounds like more of a warning against blindly copy-pasting code across projects than anything against the Ariane 4 design.
Re:fs.promises.readFile is 40% slower than fs.readFile by cutemonster on Thursday March 04, 2021 @12:50PM (#26345541)
Yes I agree.

At the same time, having added big uppercase warnings in the Ariane 4 source code and architecture docs, might have prevented this.

So, important, in safety critical code, to assume that others might blindly copy paste in bad ways -- and then try to warn them, although you might not be there any longer

Re:fs.promises.readFile is 40% slower than fs.readFile by Karunamon on Thursday March 04, 2021 @01:13AM (#26339224)
This sounds distressingly similar to the Therac-25 failures. A radiotherapy machine who's software was (blindly?) copy-pasted from a previous version of the system which had hardware interlocks to prevent unsafe configurations of the radiation emitter.

The new one did not have these interlocks, instead doing everything in software. The result of this was a few people being fatally irradiated when a certain race condition was triggered.

Re:fs.promises.readFile is 40% slower than fs.readFile by a_imho on Thursday March 04, 2021 @05:29AM (#26340780)
I know the relevant xkcd, but it is always Ariane, Therac and Mars Climate Orbiter.
Re:fs.promises.readFile is 40% slower than fs.readFile by zucker42 on Wednesday March 03, 2021 @10:21PM (#26338218)
I guess the problem is if their calculations are wrong and they are actually allocating more memory than expected.

I think a better approach (and one which NASA uses from what I've read) is to only use static memory.

Re:fs.promises.readFile is 40% slower than fs.readFile by kdtsh on Wednesday March 03, 2021 @09:59PM (#26338092)
Not at all unreasonable. You could very rightly consider any other arrangement ‘overengineered’
Re:fs.promises.readFile is 40% slower than fs.readFile by eternalban on Wednesday March 03, 2021 @10:09PM (#26338151)
Eminently reasonable: dispensing with memory management (allocate/gc) for an embedded real-time missile guidance system. It may have even had static memory layout which likely further improves performance.
Re:fs.promises.readFile is 40% slower than fs.readFile by willbudd on Wednesday March 03, 2021 @10:18PM (#26338204)
I'd be inclined not to use the heap at all though in that case. Just preallocate static arrays in each location.