Apollo-11
FizzBuzz Enterprise Edition
Our great sponsors
Apollo-11 | FizzBuzz Enterprise Edition | |
---|---|---|
126 | 329 | |
56,273 | 20,374 | |
- | 1.4% | |
4.6 | 0.0 | |
19 days ago | 5 months ago | |
Assembly | Java | |
GNU General Public License v3.0 or later | - |
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
-
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!
-
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.
-
Apollo dev posts backend code to Git to disprove Reddit’s claims of scrapping and inefficiency
Extension pack for picking up Matt Damon
- Analysis of Twitter algorithm code reveals social medium down-ranks tweets about Ukraine
-
How much we accomplished over the years
We didn't destroy the technology. A lot of the original documentation still exists. For example, all the code for the Apollo Guidance Computer is available on GitHub if you're interested.
- A difficult decision to set us up for the future
-
Discussion Thread
Can we get networking on the Apollo-11 so we can browse the DT?
-
Apple Lisa source code release
It's not "just fixing typos", as this code was generated through OCR - and the publisher specifically ask to proof-read and fix typos (https://github.com/chrislgarry/Apollo-11/blob/master/CONTRIBUTING.md)
-
We invested 10% to pay back tech debt; Here's what happened
> the code for the space shuttle should be written carefully
Couldn't help but remember the comments in the Apollo-11 source code saying "TEMPORARY, I HOPE HOPE HOPE".
https://github.com/chrislgarry/Apollo-11/blob/a13539c7c5c482...
FizzBuzz Enterprise Edition
-
Simple Lasts Longer
That "Hello World Enterprise Edition" looks dangerously under-engineered - I could understand it! Far better to follow the best practices demonstrated in the Fizz Buzz Enterprise Edition...
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
-
Writing Clean Code with FastAPI Dependency Injection
Clean code is a balancing act - you’ll want to make sure you don’t turn your codebase into something like this.
- Milyen hasznos Github repokat ismertek?
-
Java 21 makes me like Java again
???
I'll answer your question with a question: Have you seen https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... ? :)
I'm guess that to those of us who remember when Java came out, "FizzBuzz: EE" is what we think of when we think of Java. :P
In Java I have to type a bazillion characters to get anything done! And make all these useless directories and files and InterfaceClassFactoryProtocolStreamingSerializer BS. And worry about how that executes.
C++? No bloat*, just speed
*Yes, there's some _optional_ bloat. But compared to Java? no contest.
-
No One Wants Simplicity
There’s a difference between complexity that’s inherent to the problem, and complexity that’s added by developers who have drunk architectural cool aid.
This is an example where all of the complexity is caused by rigid adherence to the most popular architectural patterns of about 10 years ago.
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
It looks completely ridiculous to modern eyes, but during peak OOP it was just how you should do it.
If you like simplicity then your fizz buzz implementation would be a few lines.
-
55 GiB/s FizzBuzz (2021)
maybe it's fast, but is it enterprise quality? https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
- Ask HN: What are some of the most elegant codebases in your favorite language?
-
Another half-backed dependency injection crate
Nope, I wouldn't use it. I've seen many projects that use DI containers in my career, and every single one of them was a pain to navigate, particularly when trying to get a foothold as a newcomer. It can also force you into some very enterprise-y code patterns. Keep things simple. My mantra is "Add complexity as you find that you need it, and not a second sooner".
-
I'll use a hashmap 😛
Do you want a quick hack or a coder that's up to enterprisey standards? A proper solution could be in the 1.5 KLOC ballpark...
-
Is sequential IO dead in the era of the NVMe drive?
> you have no idea how much happens so your transaction doesn't get lost, corrupted, or errored out.
Maybe he doesn't, maybe he does - you don't know nor do I.
I'm pretty sure this is how IBM salesmen used to respond when confronted with those newfangled Unix systems which were starting to appear here and there, nibbling first, then taking larger bytes out of their market share. Instead of the litany of diverse systems they'd have thrown LPARs, SYSPlexs and ESMs around but in the end it still came down to the same thing: this stuff is too complicated to be left to amateurs. They were right, in a way... until those amateurs grew their wisdom teeth and took a large part of their market away from them.
Yes, "enterprise" stuff is complicated - often overly so [1] - and it has its place. This does not make it the only viable solution to these problems, something will eventually come up to eat your lunch just like IBM saw its herd of dinosaurs being overtaken by those upstart critters from the undergrowth. Maybe some smart software system which "guarantees" data reliability and availability without the need for "enterprise" storage devices? It wouldn't be the first time after all.
[1] https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
What are some alternatives?
Logback - The reliable, generic, fast and flexible logging framework for Java.
awesome-functional-python - A curated list of awesome things related to functional programming in Python.
Simple Java Mail - Simple API, Complex Emails (Jakarta Mail smtp wrapper)
yGuard - The open-source Java obfuscation tool working with Ant and Gradle by yWorks - the diagramming experts
bitburner - Bitburner Game
Java-Hello-World-Enterprise-Edition
is-odd - I created this in 2014, the year I learned how to program. All of the downloads are from an old version of https://github.com/micromatch/micromatch. I've done a few other things since: https://github.com/jonschlinkert.
JavaCV - Java interface to OpenCV, FFmpeg, and more
jsweet - A Java to JavaScript transpiler.
carbon - :black_heart: Create and share beautiful images of your source code
FizzBuzzEnterpris
openJDK-docker - Docker Official Image packaging for EA builds of OpenJDK from Oracle