842 karma · joined December 4, 2021
I spent some time last year digging around in Wayland and I've got to admit that I was surprised to learn that there really isn't anything really there. Like, there is no "system". I had read that "it's a protocol" but I hadn't fully internalized it. I'm honestly a bit surprised anyone has adopted it. It almost feels like a scam. :) When I checked you couldn't even get your window decorated without an extension (that Gnome decided to not support so you have to bring your own decorator there?).
> or just malloc everything all at once?
Yes! But here's the thing: this isn't done due to the footguns associated with memory management, it is done because you want as little dynamic behavior as possible. For Level A software you need to show that your software has both bounded execution time and memory usage, and be robust against all inputs. Achieving that is so much easier without dynamic memory management.
Also, another thing to keep in mind is that DO-178 has you show that your software requirements are traceable to system requirements, your software design to your software requirements, your source code to your software design and your object code to your source code. But testing should be requirements based. So if your compiler inserts a bounds check now you have object code not traceable to source code and for which you won't have coverage because your requirement mention it. But what if you mention it in your requirements? Well, then you'd have to implement it manually in source code to uphold traceability anyway...
I will caveat the above by saying that other players may interpret things differently or have found ways to do things more cleverly.
Also, tools follows DO-330 and are qualified. It's their output that should comply with DO-178.
People need to ask themselves what benefits Rust would bring to an high assurance system (e.g. DO-178C Level A). You're not gonna want to malloc mid-flight even if you have a borrow checker.
The entire point of e.g. DO-178C is to show that the software only does exactly what it is supposed to do under all assumptions and have any derived behavior fed back to the safety process for evaluation. Software can never in itself make a system safe.
All that aside, modern tooling may be more ergonomic etc so I'm not saying languages like Rust shouldn't be considered, they just aren't as useful here as I think a lot of people assume.
This very succinctly describes the entire management class here in Sweden... The public sector is run by incompetent people who have to buy consultants to do anything and the private sector is led by the same kind of people to the point where actually competent people avoid going into management. I wonder how long we can keep this up.
I will note however, that it has expanded his capabilities. Some of the tools he use are scriptable and he can now prompt his way into getting these scripts. Something he'd previously would have needed a programmer for. In this aspect his capabilities now overlap mine, but he's still not the slightest more interested in actually learning programming.
I've had similar experience with film. Just compare the stuff coming out of Hong Kong today with what came out during the 80's and 90's.
Comedy is another thing I don't see go on export any time soon...
My impression is that Chinese culture has very little appeal elsewhere (at least in the West). They can't seem to be able to (or care to) package it in an appealing way. Sure, they're being catered to in films and video games but I see very little organic interest in Chinese culture, especially compared to Japanese or Korean culture.
I don't know anything about B-52s, but I work on a project where we are essentially replacing a 40 year old weapon system with a new one. The new one should of course do the same things, preferably better, and do additional new things. The old system started out simple, but has since had most of its internals swapped both hardware and software wise a number of times. We have full access to all the documentation of the old system, but let's say there has been periods throughout these 40 years where this aspect hasn't exactly been top priority.
It doesn't come as a surprise to me that projects like JSF end up a complete clusterfuck. Everyone tends to underestimate the complexity of the system they operate/produce after a while because most of it is always there and just works.
The fentanyl industry maybe?
I have never really thought much about it, but I guess the actual LCD thingie is manufactured in one piece and the control signals just being split between different computers somehow, but I don't know anything about how these things are made! :)