Deleted Comment
No, it will just kill the browser. The fact he thinks otherwise tells me how out of touch he is.
Deleted Comment
I remember fretting about these rules when reading Scott Meyer's Effective C++11, and then later to realize it's better not to use auto at all. Explicit types are good types
const auto start = std::chrono::steady_clock::now();
do_some_work(size);
const auto end = std::chrono::steady_clock::now();
const std::chrono::duration<double> diff = end - start;
std::cout << "diff = " << diff << "; size = " << size << '\n';
Looking up the (current standard's) return type of std::chrono::steady_clock::now() and spelling it out would serve no purpose here.Mil/gov customers are still die-hard GPIB users and that's a major sector for T&M sales.
That said I think the wiring there is still thick aluminum.
Not sure I really have a point - all things equal I'd prefer copper, but it seems like aluminum can be fine when done right too - just riskier when done to the quick and dirty homebuilder standard.
I know nothing about grease, but it's pretty obvious that a fuse was missing. You might want to check that such of correct rating is in place now.
Made for a good story, reality is a bit more complex methinks. There's after all a lot of money to be made with war.
Deleted Comment
CCL, as far as I can tell, is abandonware
Last release was August 14 2024. For a 30+ year old project, that's quite recent methinks.
It clearly doesn't move as fast as SBCL, but I wouldn't call it abandoned either.
ototh, afaiu, SBCL gave up on ARM32. Can't blame them for that, but until 2023 I was still using an early Banana Pi with such. CCL worked there much better (also it's GC seems more robust).