Menu
Forums
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Trending
What's new
New posts
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Upgrades
Log in
Register
What's new
Search
Search
Search titles only
By:
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Server Development
Habbo Retros
Habbo Development
Kirsikka - A bridge between modern and oldskool
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="LeChris" data-source="post: 452695" data-attributes="member: 37998"><p>That specific era you're building arounds looks to be around the <strong>R59</strong> era of Habbo. So use that if you want to provide better clarification instead of saying "between old and modern habbo." </p><p></p><p>In regards to the code itself, I'm a bit confused. Your server seems to follow good programming practices in terms of the high level stuff. Dependency injection, web sockets, etc. Which brings me to the utterly confusing client. </p><p></p><p><strong>Rants</strong></p><p>Are you doing the client in plain JS without the use of any frameworks, libraries or even jQuery out of ignorance/ as a beginner to learn the language fundamentals? I cannot think for the life of me of any reasons to build a long term app that will easily reach hundreds of files, in plain JS without any libraries once so ever. I mean, not even lodash and ES4 on top of it all? </p><p></p><p>If you intend on this development</p><ul> <li data-xf-list-type="ul">Looking and functioning great</li> <li data-xf-list-type="ul">Being stable and performant </li> <li data-xf-list-type="ul">Being scalable dev wise and production wise</li> <li data-xf-list-type="ul">Looking good on your portfolio</li> <li data-xf-list-type="ul">Building experience</li> </ul><p>Then you need to switch to use Typescript with libraries. Maybe even switch the whole style to TDD (Test driven development) which is fucking bonkers on how stable it makes everything (bug wise). What shouldn't happen is you continue to write in old JS with the lowest amount of 3rd party resources. There is 2 levels to being a developer. The junior who questions and doesn't trust any library and believes learning the language to re-invent said library is better; or the senior who understands why these libraries exist, knows how they work and knows to use them when appropriate (hint: this is a perfect time to use it)</p><p></p><p>RAW JS should only be used maybe on a my little pony portal to show sparkles around your form inputs. Anything beyond that 9/10 could easily benefit from a library or definitely a framework. </p><p></p><p><strong>Advice</strong></p><ul> <li data-xf-list-type="ul">RAW JS is bad. You need to switch to either Typescript or just writing ES2019</li> <li data-xf-list-type="ul">Lack of types is bad. See above about switching to TS. This greatly improves stability by removing questions in run time by checking in compile/transpile time.</li> <li data-xf-list-type="ul">Lack of libraries is <strong>horrible</strong>. You should definitely throw libraries where problems can be solved with them. Don't do a HTML5 client in raw canvas, you'll hate yourself in a few months when your drinking problem kicks off from it.</li> <li data-xf-list-type="ul">Do not hate libraries without any reason. I wasted 5 years of development believing I could do it better, provide a more cutting edge performant solution. Truth is, a library adds maybe half a millisecond which isn't noticeable to anyone but perhaps a super intelligent alien from Area-51 who may blink at this. JS itself isn't great on performance, so using libraries isn't going to restrict it from being itself. Web development is only growing in how hard it is to do front end things, WASM is launching full force and will soon carry over a lot of compatibility and libraries which will make TS look like a little bitch. Don't self deprecate this project by using old practices.</li> <li data-xf-list-type="ul">Import JSON files, don't do that weird $.getJSON() thing. I don't know what it is as I never used jQuery but it looks like it's a worthless function that could be replaced with the core solution <strong>import x from './config.json'</strong></li> <li data-xf-list-type="ul">Why the weird things sometimes? ie: Declaring an empty array then pushing values to it which look like that's always the main case. Why not just declare it with the new Credits() and stuff in it as a constant? Immutable is always nice </li> </ul></blockquote><p></p>
[QUOTE="LeChris, post: 452695, member: 37998"] That specific era you're building arounds looks to be around the [B]R59[/B] era of Habbo. So use that if you want to provide better clarification instead of saying "between old and modern habbo." In regards to the code itself, I'm a bit confused. Your server seems to follow good programming practices in terms of the high level stuff. Dependency injection, web sockets, etc. Which brings me to the utterly confusing client. [B]Rants[/B] Are you doing the client in plain JS without the use of any frameworks, libraries or even jQuery out of ignorance/ as a beginner to learn the language fundamentals? I cannot think for the life of me of any reasons to build a long term app that will easily reach hundreds of files, in plain JS without any libraries once so ever. I mean, not even lodash and ES4 on top of it all? If you intend on this development [LIST] [*]Looking and functioning great [*]Being stable and performant [*]Being scalable dev wise and production wise [*]Looking good on your portfolio [*]Building experience [/LIST] Then you need to switch to use Typescript with libraries. Maybe even switch the whole style to TDD (Test driven development) which is fucking bonkers on how stable it makes everything (bug wise). What shouldn't happen is you continue to write in old JS with the lowest amount of 3rd party resources. There is 2 levels to being a developer. The junior who questions and doesn't trust any library and believes learning the language to re-invent said library is better; or the senior who understands why these libraries exist, knows how they work and knows to use them when appropriate (hint: this is a perfect time to use it) RAW JS should only be used maybe on a my little pony portal to show sparkles around your form inputs. Anything beyond that 9/10 could easily benefit from a library or definitely a framework. [B]Advice[/B] [LIST] [*]RAW JS is bad. You need to switch to either Typescript or just writing ES2019 [*]Lack of types is bad. See above about switching to TS. This greatly improves stability by removing questions in run time by checking in compile/transpile time. [*]Lack of libraries is [B]horrible[/B]. You should definitely throw libraries where problems can be solved with them. Don't do a HTML5 client in raw canvas, you'll hate yourself in a few months when your drinking problem kicks off from it. [*]Do not hate libraries without any reason. I wasted 5 years of development believing I could do it better, provide a more cutting edge performant solution. Truth is, a library adds maybe half a millisecond which isn't noticeable to anyone but perhaps a super intelligent alien from Area-51 who may blink at this. JS itself isn't great on performance, so using libraries isn't going to restrict it from being itself. Web development is only growing in how hard it is to do front end things, WASM is launching full force and will soon carry over a lot of compatibility and libraries which will make TS look like a little bitch. Don't self deprecate this project by using old practices. [*]Import JSON files, don't do that weird $.getJSON() thing. I don't know what it is as I never used jQuery but it looks like it's a worthless function that could be replaced with the core solution [B]import x from './config.json'[/B] [*]Why the weird things sometimes? ie: Declaring an empty array then pushing values to it which look like that's always the main case. Why not just declare it with the new Credits() and stuff in it as a constant? Immutable is always nice [/LIST] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Server Development
Habbo Retros
Habbo Development
Kirsikka - A bridge between modern and oldskool
Top