apollo-backend VS Apollo-11

I believe this endpoint is the only way to retrieve json with posts from Reddit, so every single app would use it. Even Apollo used it, although it did it with OAuth. See this line:

https://github.com/christianselig/apollo-backend/blob/ab04b2...

Disclaimer: it's been quite a while since I've last looked into Reddit API, so I could easily be wrong.

I'd consider platform and infra tools the kind of projects that require DSA. As for product, this is the typical kind of projects I've worked on: https://github.com/christianselig/apollo-backend which doesn't have any LC stuff. But I get that things are very different in big tech / FAANGS.

Since Apollo’s backend server is now open sourced, it'd be great if we could install the server on a Raspberry Pi or something so one can get notifications and other features that rely on it.

5. Apollo Backend: - Set up an Apollo backend server using a community-driven platform like https://github.com/christianselig/apollo-backend. - Design and implement the backend infrastructure for SecurIoT, including data storage, authentication, and API endpoints. - Integrate the backend with the frontend components of SecurIoT. - Thoroughly test the backend functionality, ensuring it supports the required operations and scalability.

The Backend was open sourced to counter U/spez Bullshit arguments about inefficient code creating too many API requests

See here https://github.com/christianselig/apollo-backend

On this same call, Huffman claimed that Apollo employed "scraping", a technique of programmatically fetching a webpage to process its contents.[d] Scraping is largely considered bad practice in web resource development, as it is not using resources as they were intended, and can be costly to the party being scraped. This is especially true when the same data is available via an API (Application Programming Interface), which is the intended method of programmatically fetching website content. Christian refutes Huffman's accusation, and has open-sourced Apollo's server code to prove it does not scrape reddit. I have seen no credible claims or evidence that Huffman is correct.

You could totally do everything you want to, except it's not as simple as making Reddit API requests because there's this: https://github.com/christianselig/apollo-backend

Apollos is here https://github.com/christianselig/apollo-backend

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!

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...

You can look at the Colossus 2A code written by Margaret Hamilton and her very small team on Github.

"Burn Baby Burn" might be even more apt!

https://github.com/chrislgarry/Apollo-11/blob/master/Luminar...

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.

Thankfully it was eventually migrated to GitHub