How much JavaScript can really be loaded into memory by the browser?

Question

I am working on a BIG project written in RoR with a jQuery interface. I am adding AngularJS, which has an intelligent dependency injection, but what I want to know is how much javascript can be put on the page before the page becomes noticeably slow? What are the specific limitations for each browser?

Assuming that my code is well accounted for and all operations are performed in constant time, how many functions, objects and other things can I allocate in javascript before the browser reaches its limit (which should be one, because any computer has a finite amount of RAM and disk space (although disk space would be an ambitious limitation for javascript)

I looked online, but I only saw questions about how many people they can upload, i.e. how many megabytes I can upload, etc. I want to know if there is an actual limiting level of calculations set by browsers and how they differ

- EDIT -

For very critical, I think the best question is:

How does a modern web browser determine the limit for the resources it allocates for a page? How much memory can I use for a web page? How much disk space can a page use?

Obviously, I am using AJAX, I know a decent amount to optimize rendering. It is not a question of how I can make my page faster, but rather, what is resource limitation?

Answer 1

, . !

, JS, , , , .

, , , , / .

, AJAX, , .

Answer 2

, javascript, . - javascript, , , .

, , 3 60 ( ), . ​​, , , , , . RequireJS (, ), , , - , , .

, "" , . , , , , html. . , . "onClose" , , , , . . - window.app.data = {}. , . . "" , . .

, , . , , , , , .

Answer 3

, - , .

.

In addition, slower devices sometimes run outdated and / or less feature-rich browsers, so you can do some basic user checks or discover features on the client and return to the plane-rendered HTML server.