Then just ask it.
Printable View
Awesome, guys! Really good!
4 days since last update post. I expected a lil more from a starting development team.
Regret to inform that I'll be stepping down from this project. As it stands I've finished most of the ground work but nobody else (with the exception of Adil) seems to be interested in actually working on the project. I'm moving onto another area of focus, hopefully it'll result in some pretty awesome stuff for the community.
Best of luck to the Azure team. I'll be around if you happen to need help with debugging.
Sent from my iPhone using Tapatalk
And there goes Azure...
To correct this misunderstanding, Scott mainly worked on improving what I had already laid out as a foundation, as I wasn't as experienced with netty 4, he worked on "improving" our codec, as well as our packet manager, not the whole solution.
As sad as it is to wish him a goodbye from the development he feels as if no one is progressing or whatever way he feels, that is his decision. Me, Adil, Dominicus, and others are continuing the development and there hasn't been any recent updates due to the fact that the Database was/is being written (Adil) so we're going to wait for everything to be done and structured before proceeding...
Another thing, we're switching (downgrading) to netty 3.x and this decision is final until further objection. Due to careful profiling and several benchmarks we feel that this would have a substantial performance impact on the overall networking.
So you are already designing your database without having a design for your emulator?
You guys are really going fubar on this emulator.
Haha. GG. Its probably just that you cannot read documentation. Netty 4 outperforms Netty 3 easily. Its just that you cannot deal with the code that scott wrote.
Most likely you downgrade so you can copy over the socket implementation from Habbo4Java.
As tempting as it is to make you look like a complete idiot (not that you don't do that yourself), I've wrote a network handler in netty 3 along time ago, and I've gotten fair compliments from it, so that's one of the reasons.
Secondly, as ignorant as you sound when you tell us we don't have a design for our emulator when we've mapped out every file, folder, class, interface, etc... I won't even address that.
Thirdly, what the fuck does "fubar" even mean? Nobody understands your slang pal.
Fourthly, Scott was a member of our team. I don't think you know what the word "team" means, so let me inform you:
Google: "a group of players forming one side in a competitive game or sport."
And I actually wrote the networking classes, not Scott... as I've stated before.
And Netty 5 documentation simply makes Netty 4 look like a pile of shit, does that mean you should use 5.x over 4.x?
I'm surprised that there's no comments explaining how methods work, considering this is a group project it's important that you let your other members know how a function works.
Meh, the source code wasn't bad. I was really displeased at the source, one of the reasons I lost interest in the development.
But you're wrong about the "comments" part. We document where documentation is needed. So far there hasn't been a need.
Writing redundant comments that tell you the same thing that the name of the method tells you say "readString()" then you have commented "Reads a string.", that's just stupid. "Poor documentation, is the same as no documentation."
Still wondering how you've managed to obtain the source. But, I've been working on a new source so I'm not so fussed.
You don't know what design means in the software development world.
https://en.wikipedia.org/wiki/Software_designQuote:
Software design usually involves problem solving and planning a software solution. This includes both low-level component and algorithm design and high-level, architecture design.
But that's probably considered 'too much work so we do not waste our time on that'. No you cannot already build the whole database without even knowing your inner core structure. If you do that you're guessing and assuming how it is going to work and once mistakes are made you're wasting your time on recovering from those mistakes by adapting your database to the problem (Which I doubt you gonna do so you end up hacking solutions again).
Let me google that for you
Netty 5 is in Alpha. If you could read you'd know.
I've my doubts about this 'team'.
You're already giving up?
Oh boy. This is the biggest mistake you can make. Especially in a team.
No that's not stupid and not only should you tell what it does, also document its parameters. Poor documentation means poor developers resulting into a poor piece of software.
Ah maybe one of your 'developers'. You? Does your team know about that you starting over again? Sounds like a good decision when your database implementation isn't even ready.
I'mma just leave this here. Feel free to judge for yourselves. https://mega.nz/#!fxxlSKIB!GnJlWPgh_...RE5unDwjTLQoLA
That's simply not true.
- None of the encryption classes are documented
- Encoding is not documented
- The bootstrap isn't documented (and it's a big class).
- Session class isn't documented (eg, could explain the difference here between sendQueued and sendMessage)
I could go on, but I've proved my point.