Apollo-11
React
Our great sponsors
Apollo-11 | React | |
---|---|---|
127 | 1,687 | |
56,371 | 221,535 | |
- | 1.0% | |
4.6 | 9.8 | |
about 1 month ago | 2 days ago | |
Assembly | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Apollo-11
- Original Apollo 11 Guidance Computer (AGC) source code
-
Mistral CEO confirms 'leak' of new open source AI model nearing GPT4 performance
I often like to think about https://github.com/chrislgarry/Apollo-11 as an analogy. It's public domain with available source, in the assembly language in which it was written... so it fills all the definitions of OSS!
But the process by which that code arose, the ability to modify any line and understand its impact (heh) on a real execution environment, is dependent on a massive process that required billions of dollars and thousands of the smartest people on the planet. For all intents and purposes, without that environment, it is as reliably modifiable as an executable binary in any other context - or a set of weights, in this one!
-
Can a Transformer Represent a Kalman Filter?
But can a Transformer run on the Apollo Guidance Computer?
https://en.wikipedia.org/wiki/Apollo_Guidance_Computer
Frequency 2.048 MHz
Memory 15-bit wordlength + 1-bit parity
2048 words RAM (magnetic-core memory)
https://github.com/chrislgarry/Apollo-11/blob/master/Luminar...
-
TIL an Oxford University physicist claimed that for the moon landing conspiracy to be true, around 411,000 people would’ve needed to keep it secret. He also suggests the hoax would’ve broken down in 3.68 years.
You can look at the Colossus 2A code written by Margaret Hamilton and her very small team on Github.
- "Temporary" code in Apollo 11's lunar landing guidance equations (1969)
-
SpaceX poised for 'mid-November' launch of second Starship test flight
"Burn Baby Burn" might be even more apt!
https://github.com/chrislgarry/Apollo-11/blob/master/Luminar...
-
Software Disenchantment
My more positive take on this: our runtime environments are bloated because we have ways to enable trust, stability, and iteration speeds that people wouldn't have dreamed of in years past.
Your Notion desktop app and Google Chrome both support embedding & displaying multimedia content that's controlled by people that you may not trust, but they can draw on decades of engineering to sandbox that content. They can independently be updated without worrying about a centralized `flexbox.dll` that may or may not be the right version. They do not require building a new executable to make the vast majority of UI changes. And the cost is simply storage space and initial download bandwidth.
We can look with rose-colored glasses at an era of "every byte of assembly has been hand-crafted." I, too, look in awe at what was achieved with such things as https://github.com/chrislgarry/Apollo-11/tree/master/Luminar... . But that software, per https://en.wikipedia.org/wiki/Apollo_Guidance_Computer#Softw..., took 1400 person-years of work.
We have to compare apples to apples - the abstractions we have today would not prevent such a piece of software from being built, and indeed would allow us to build that exact software, even bit-for-bit the same, much more easily due to abstractions on our tooling itself. We have not departed a world where, given a nation-state budget, one could pay for 1400 person-years of work and create the AGC (though one might make arguments about the distraction levels of modern society, but that's a different thing entirely).
But we also exist in a world where I can build and ship a cross-platform video chat application in an afternoon (well, not counting app store approvals) and be reasonably confident that my app will be compatible with, and secure on, practically any computer or mobile device sold in the past half decade, regardless of how many other apps may have been installed on each device. I'd venture to say that Apollo engineers would, and do, find this aspect of our world fascinating, too.
- NASA's Voyager Team Focuses on Software Patch, Thrusters
-
Margaret Hamilton stands next to her handwritten code for the lunar missions
Thankfully it was eventually migrated to GitHub
React
-
Integrate Bootstrap with React
This article serves as your comprehensive guide to mastering the art of combining Bootstrap and React seamlessly. Dive in to uncover the tips, tricks, and best practices to elevate your UI design game effortlessly.
-
React Server Components Example with Next.js
This isn’t an accident; when Meta introduced React Server Components, Dan Abramov explicitly stated that they collaborated with the Next.js team to develop the RSC webpack plugin.
-
Collab Lab #66 Recap
JavaScript React Flowbite Tailwind Firebase - Auth, Database, and Hosting Vite
-
New Features in React 19 – Updates with Code Examples
Official Website Team GitHub Canary Releases
- Web Components e a minha opinião sobre o futuro das libs front-end
-
7 Frameworks, One SAML Jackson - Your Open Source Single Sign-On Solution
In the JavaScript ecosystem, there are guides for enabling SAML-based enterprise single sign-on in AdonisJS, Express.js, Next.js, Remix, and React with an Express.js backend.
-
Type-Safe Fetch with Next.js, Strapi, and OpenAPI
What you have seen now works great especially when you are fetching data on the server, like in React Server Components using Next.js. But data fetching on the client side is often a bit more involved. At least what you want is for example some data loading indication and to know when the data is actually available in the client.
-
Optimizing React Apps for Performance: A Comprehensive Guide
In addition to being a best practice, performance optimization in React is crucial since it affects the user experience directly. The speed and responsiveness of your React app are critical factors in determining its level of success in the modern digital world, where customers want seamless, quick, and uninterrupted experiences.
-
Building a Dynamic Job Board with Issues Github, Next.js, Tailwind CSS and MobX-State-Tree
Familiarity with TypeScript, React and Next.js
-
Building a Fast, Efficient Web App: The Technology Stack of PromptSmithy Explained
We all know what React is at this point, but why use it with Vite and React Router DOM over something like NextJS?
What are some alternatives?
DOOM - DOOM Open Source Release
qwik - Instant-loading web apps, without effort
microwatt - A tiny Open POWER ISA softcore written in VHDL 2008
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
midimonster - Multi-protocol control & translation software (ArtNet, MIDI, OSC, sACN, ...)
Vue.js - This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core
WebKit - Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
SvelteKit - web development, streamlined
Godot - Godot Engine – Multi-platform 2D and 3D game engine
lit-element - LEGACY REPO. This repository is for maintenance of the legacy LitElement library. The LitElement base class is now part of the Lit library, which is developed in the lit monorepo.
OpenSkyStacker - Multi-platform stacker for deep-sky astrophotography.
Tailwind CSS - A utility-first CSS framework for rapid UI development.