Ummm.... current MS windows is ~ 50million lines of code. 30%-40% debugging is between 15-20million lines of code. Hopefully, 30%-40% debugging of 15-20 millio

Ummm.... current MS windows is ~ 50million lines of code. 30%-40% debugging is between 15-20million lines of code. Hopefully, 30%-40% debugging of 15-20 million lines is not done all in one sitting. Changing to an embedded OS, say kontiki OS under 5,000 lines of code, would make for debugging only about 1,500 to 2000 lines, or about a 10,000 fold reduction by dropping 10's of millions of code libraries. On the other hand, first recorded bug was pretty easy to see/fix. https://www.nationalgeographic.org/thisday/sep9/worlds-first-computer-bug/ https://www.nationalgeographic.org/thisday/sep9/worlds-first... Back in the day, when soft-ware was wool via jacard loom, finding issues introduced by bug(s) (aka month holes) was a true enlightening/loominating process -> shine light behind woven wool cloth & look for the light spots. Of course, fixing the bug issue(s) meant breaking out the crochet needles to mend the problem. Pearl was taken pretty seriously then. short take: even if https://hackaday.com/2021/03/08/laser-zap-that-mosquito/ https://hackaday.com/2021/03/08/laser-zap-that-mosquito/ works 100% of the time for 100% of the bugs; the unseen bugs will still make it through.