Closes #20 - transition to C++ and solve HTML templating #24
No reviewers
Labels
No Label
bug
Critical Priority
duplicate
enhancement
help wanted
High Priority
invalid
Low Priority
Medium Priority
Meta
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Cavemanon/cavecomm#24
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "cpp"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Java's verbosity and analness has made developing this tool not as efficient as it could be. So, I opted to (in one sitting), rewrite everything we had (and then some) while knowing none of the tools I was using.
This happened because of Vertx' poor documentation with its template system. Learning everything with poor documentation took forever, and since java is pedantic with its syntax, there was a lot more room for error, and that error held up actually writing the tool.
I swapped to C++ to just see if the issue was with my understanding of the tools or the tools I was using. I succeeded in writing all this in one sitting without blowing my brains out (although C++, at times, did make me want to throw myself out a window). So, I'm pretty sure the tools we're using are holding up development.
C++ sucks, but Java sucks way more. This rewrite has templating, SQL data insertion, SQL data reading, along with a make file for building the system (and the SQL database, assuming you're running Debian). It's not great in terms of security, but works as a proof of concept.
@t_a, I'd like to hear your opinion on this change (and if its worth going for), or if we should stick with Vertx despite its flaws.