I am mostly using JavaScript on my scripting. I have some scripts that do several things every 1 second, And some 0.02 seconds etc. My intervals work like some internal HTML, small animations, and so on. Now I have 4, but I think it will increase in future; Maybe I'll control myself for less than 10 years. Although it is not in my computer at all.
- Generally, would it be good for the site?
- Since this client-side will obviously not have any problems with the Internet connection, okay?
- Is this a bad habit, or is it not an issue at all?
In addition, I have a question for jQuery. There are things that normal JavaScript and jQuery can do in the same way (like internal HTML and .html), right? Looking at this situation, should I use Java or Javascript?
Thank you.
Too many set timeouts () are good? : You have already given your own answer too much is not good, even if you talk about it. / P>
Normally this would be good for the site : Probably not, remember that you do not know your users' CPU / browser combo, so you should create your own site so that they are still It would be good for people to use that you have slow computers
Since this client-side will not have any problem with the internet connection, okay? OK, unless there is a lonely / unresponsive site, you request network as part of the timeout
Is this a bad practice, or is it absolutely an issue is not? Bad architecture is bad behavior. If you want to follow best practices, then read on design patterns.
Also, I have a question for jQuery. There are things that normal JavaScript and jQuery can do in the same way (like internal HTML and .html), right? Looking at this situation, what should I do, jQuery or Javascript should be used? gives you convergence crossbrowser compatibility using jQuery. In most cases, the use of non-specialists is better than using a library like jQuery.
Comments
Post a Comment