Sephus Posted October 4 Share Posted October 4 So, I know that this is the most common topic that there can be in our community but I want to be the one who first starts a topic about it. Simply because I created it. Horizon is a really good state-of-the-art RO emulator. I say really good because I've designed it and being realistic in my goals as a software engineer, I can tell that most of the work gone into Horizon is really state-of-the-art, modern, philosophically correct and marvelous when it comes to software engineering. After working on software on my own, I know what is good software and what kind of programs are good in their architectural engineering what which programs really suck. I know which are the good and bad parts of the program and which can be rewritten. So when I say that Horizon is good software, I'm saying that it is architecturally really good. I'm not going to compare it to another emulator in this topic because it is not the reason for this conversation but it is definitely a topic that is slipped under the rug. Nobody wants to get into a debate when we're just trying to have a conversation. What I really want from this conversation is for it to be about is the quality of software, without comparing it to the other emulators, because we know how the emulators run. We don't want it to be about them. But by analyzing and making observations about the pieces of logic that have gone into creating several thousands of components of the software. If you are a technical reader and are reading this, I'm sure you would love to understand how parts of a software work and why they work that way. The more we delve into the subject the more we are entertained. If you are a pure tech junkie that is. I am. That is why I want to promote such a topic. For example, I have a component A that is logically interacting with component B. They are both required functions of the software and to elaborate on their functionalities, we note down the systems at hand and compare them side-by-side. By the end of the comparison, we derive what relations are formed between the two components and why, with their reasons. I want logic to be meaningful because relations are important, and they lead to meaningful connections. So, to sum it up, we land ourselves in a conclusion that component A for reason C is connected to component B, having so and so functionality of D. Not only do we clarify that the components by themselves have individual functionalities, but also collectively generate a new function in the design of the software we are creating. So, building from A and B to C and D we create a new functionality E that powers another component F and they have a relation G. And so on and so forth. Logic is very interesting and how it meaningfully adds up is the most interesting thing that I have understood in my life. I want to share the knowledge with you and for the same reason create my own life around software. Just sharing these two bits of knowledge with you so that we can start a conversation and let it build and create more interesting topics which flow into a cultural habit for us, here in the Horizon community. Thanks for reading, Sephus. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.