Replies: 4 comments
|
Thank you for the kind words, appreciated! 👍 Many other current projects are often indeed built on top of pre-existing projects, causing different code styles and architectures throughout the years to merge together which can make it hard to comprehend it as a whole, especially for new people. I'm happy to hear that the OGameX codebase is easier to understand for you. 😄 |
|
Brother, why don't you use more advanced front-end frameworks? For example, Vue. |
|
https://og.jntm.cool/ |
|
My goal for this project is to stay true to the original game and preserve the original front-end as much as possible, hence why implementing Vue/React/NextJS and such frontend frameworks are not part of the scope currently for OGameX. I have migrated this issue to the |
Uh oh!
There was an error while loading. Please reload this page.
Recently, I took a look at your project code, and it was truly an eye-opener! The code structure is clear, naming conventions are followed meticulously, comments are thorough, and the modular design is executed flawlessly. In contrast, the 2moons and new-star projects I've dealt with before are like the fighter jets of "code mountains" – a chaotic pile of code where fixing a bug feels harder than climbing to the heavens.
Your project code can only be described as "elegant." Each function is concise and focused, adhering to the single-responsibility principle; variable names are so intuitive that there's no need for guesswork; and the comments not only explain "how" something is done but also the "why" behind it. This kind of code is not only easy to maintain for yourself but also allows others to quickly get up to speed when they take over.
On the other hand, 2moons and new-star are like a pot of messy stew. Global variables are scattered everywhere, functions stretch hundreds of lines long, and the logic is so deeply nested that it makes you question your life choices. To make matters worse, some of the comments are outright wrong, and debugging almost made me rage-quit on the spot. These projects are a programmer's nightmare.
In comparison, your project is a beacon of professionalism in the industry. It not only highlights the importance of code standards but also made me realize that writing good code is not just a responsibility to oneself but also to the team. After all, no one wants to be stuck late at night, staring at a pile of incomprehensible "code mountains" and silently shedding tears, right?
Code standards are not a constraint but an art. They make projects easier to maintain, extend, and collaborate on. I hope all programmers can follow your example and write clean, elegant code, staying far away from the horrors of "code mountains"!
All reactions