Quote: Why would the webhost care if you split your code up?Well, if I make a separated JS file and a CSS file along with the HTML file, the browser will have to connect to the server three times to download all of them, and now it only has to connect once. Isn't that how it works?
Quote: You should invest all the time it takes to redo things properly, preferably using only .css for formatting the UI.I mean, the primary reason I can't change the appearance of my app is that I was using loads of absolute positioning inside the CSS. Is there an alternative to it for such apps?
Anyway, in the meantime, I've created another web-app to practice the design and code-structuring on. I suppose it's easier to start doing something from scratch than to try to correctly structure the 2000 lines of badly structured code, especially since I only have a very vague idea what a well-structured code is. This new app converts arithmetic expressions to assembly (unlike linguistics, that's something we both know about). Right now, it's 500 lines of code, almost all of it is the competitive-programming-style implemented algorithm (it does no input validation and is hard to extend) in JavaScript.
http://flatassembler.000webhostapp.com/compiler.html
So, do you have some ideas for it that are easy to program? And how should I program them?