|
Using a years old version and "provide a stable Apollo beginning base for those who want to move out of 317" is a bad direction
Interesting. Good luck chaf
Best of luck mate!
It might be worth considering forking Apollo and looking at it as an API rather than a base to work off of. This way you can use Apollo as a dependency and pull changes when they are made.
Best of luck Charlie look forward to seeing progress pics in discord again
I could do these things and I should use the latest Apollo, but the core aim of this project in particular is to use Apollo (whether it's updated to wherever that is now, or if it's used in any scenario that isn't this one) to build new systems instead of relying on others (Arios, Hyperion) like I have in the past. There's a million different ways that I could tackle this project, and while this isn't the best way to do it, it's my preferred way. I appreciate the suggestions and concern, but I'm trying to learn, not just the framework, but beyond the framework itself and to change that direction after selecting this one would be detrimental to my motivation to see this current iteration through.
That being said, I program as a hobby and for entertainment, and take pride in anything I do, as I've been completely self taught from day one, and I realize I can make mistakes or not pick the best direction, and that's perfectly okay for me.
gl my friend
Whether they do or don't isn't the end goal of the project, in fact making the code public was a last minute decision when I built the thread, but thanks for outlining why using a "years old" Apollo is detrimental, I'll be sure to consider your counterpoints in the future
« Previous Thread | Next Thread » |
Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |