example-chrome-extension VS virtualagc

Shameless plug: I was totally dissatisfied with the state of extension documentation and tutorials, so I wrote a book on building Chrome extensions: https://www.buildingbrowserextensions.com/

I was enthusiastic enough about extensions that I decided to publish a book about building them: https://www.buildingbrowserextensions.com/

Browser extensions are severely underrated as a platform because they aren't sexy. For all that mobile devices have given us, so much of our work continues to be done using a desktop browser. Enhancements such as augmenting websites with widgets, supplying contextual information, and automating repetitive tasks using the authenticated session - when applied appropriately - can save someone hours every day.

Browser extensions. Not quite a website, not quite a mobile app, and surprisingly pervasive. Most people don't realize how incredibly powerful they are, even with manifest v3.

I almost fell out of my chair when I found out there were no books on how to build them, so I wrote one: https://www.buildingbrowserextensions.com/ It was incredibly enjoyable to go through the APIs and write about all the different crazy things they can do.

I was frustrated with the lack of resources, so I'm publishing a book on it: "Building Browser Extensions". Available later this year. https://www.buildingbrowserextensions.com/

And check out the companion extension: https://www.buildingbrowserextensions.com/b2x

I don't think that's a great example.

For instance, I can step through and even modify that code using tooling like AGC emulators like this one http://www.ibiblio.org/apollo/#gsc.tab=0

What makes it open source is access to the same level of source access that the original developers worked in.

That's what's missing here. Mistral's engineers do not simply open this binary in their editor to do their job.

Glad you're enjoying the videos! I'm Mike from them. :) The Apollo 14 code I linked above was reconstructed in the same way as Luminary 69/2, but the process was far, far too involved for a video. Like I said above, I probably won't be much help with math, but I'd be more than happy to assist with finding documentation or navigating AGC code whenever you want!

The fact that all the information about the computer and software is public and you can verify it yourself like thousands of people have. https://www.ibiblio.org/apollo/

If you’re curious about the the technical specs of the AGC check out Ron Burkey’s website, it’s even got the source code for you to see for yourself: https://www.ibiblio.org/apollo/

Of course you should be able to tell us because all the hardware architecture and software can be found here. So you must have fully reviewed it and located the issues. Right? Than please point out where the error is.

It had manually encoded ROM in the form of "core rope memory", which is pretty wacky, but it was a digital computer. In fact, it was the first IC computer.

You can learn way too much about it and even operate (a simulation of) one here: http://www.ibiblio.org/apollo/