One of the best books I have read in recent years, somehow immensely relevant now: _Eccentric Orbits: The Iridium Story_ by John Bloom, that explores exactly what went wrong, the bankruptcy filing and so on. I wonder if you might find your experiences reflected there.
> "highly paramteric like fastners, gears, 3D printed boxes"
1. These parts should probably be on McMaster. If you are not using them straight from there, you better have a _great_ reason as to why not when it comes up in the design review.
2. Solidworks has Smart Fasteners, Inventor has Spur Gear Component Generator, Sketch->Extrude->Shell takes 30 seconds, so not sure why 3D printed boxes would be faster or better with this for most stuff. Also, this stuff is easily solved by things like the component library and configurations.
There is also all the helpful work that Mathworks does such as Simulink ...
Also, consider that MATLAB works much more like how one would write on paper (including 1-indexing) and is what people are used to at this point.
> If an engineer came to you and said “So for this project, I put all the code, input data, output data and comments scattered about one big two-dimensional array with no type safety, no portability, no scalability, no security, no variable names, no code re-use, no unit tests, no integration tests, no abstractions and no error handling”
So, how is this different from engineers and MATLAB?
Irrelevant but spreadsheets have always struck me as one of the most beautiful pieces of software that we use. Automatically updating calculations, programming logic complex anough for most ERPs, using it is a database, easy organisation of data, graphs -- it has it all. From both a user and developer perspective, they are one of the most diverse tools on a computer. MS may make terrible software sometimes, but damn it, does Excel run the world.
> Interviewer: “What happens if you allocate memory with C’s malloc and try to free it with Rust’s dealloc, if you get a pointer to the memory from C?”
> Me: “If we do it via FFI then there’s a possibility the program may continue working (because the underlying structs share the same memory layout? right? …right?)”
I see it as beautiful the same way Galadriel would be beautiful as the Dark Queen. Utterly captivating and powerful, and yet something that should never be.
My first thought was that this was done with consideration for mobile phones, since many higher-end models use 120 Hz displays, but Ladybird does not seem to support mobile for now.
> Websites using requestAnimationFrame now render at up to 120Hz on supported hardware
But the phrasing of it about "can now" suggests to me that this may simply be a performance issue too. They changed it from 60 to 120. Perhaps in the future they can go from 120 to 144 or even 240.
> the future of SQLite is basically guaranteed on account of being open source
I am not concerned with whether it has a future. But I do fear that the absolute manic focus on code quality, testing and support may take a dive when other programmers take the helm. I am not claiming that there are no developers who are equally careful and/or skilled, but whether the culture of SQLite will persist is, to me, still an open question.