I may have explained wrongfully. Your "browser" struggles to load too much text and JS is actually doing the "processing" for syntax highlighting and formatting - depending on the implementation but currently they do so on your machine still which leads to browse being non responsive and stuttering. This may be different now as they do better implementations like partial processing but how would server do the search and formatting for you?
And the point being these "browser" made are also running under your machine when running VS Code and I clearly see the difference in performance and stability when using large files. It's rare to do so but in the end, no they don't do processing for you, it's JS that gets trigger in these situations and browsers still don't like too big files + it's also letting JS get a go with it.
There might be a way to solve it by constantly sending instructions to server and getting back pieces to replace. Now I wonder how would it work when you hit formatting on a huge file? It sends back basically the whole file.
Sure thing. Honestly I would love smooth online editing so I can work from private PC without code or tools ever touching my hardware but I'd rather wait couple of more years
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I may have explained wrongfully. Your "browser" struggles to load too much text and JS is actually doing the "processing" for syntax highlighting and formatting - depending on the implementation but currently they do so on your machine still which leads to browse being non responsive and stuttering. This may be different now as they do better implementations like partial processing but how would server do the search and formatting for you?
And the point being these "browser" made are also running under your machine when running VS Code and I clearly see the difference in performance and stability when using large files. It's rare to do so but in the end, no they don't do processing for you, it's JS that gets trigger in these situations and browsers still don't like too big files + it's also letting JS get a go with it.
There might be a way to solve it by constantly sending instructions to server and getting back pieces to replace. Now I wonder how would it work when you hit formatting on a huge file? It sends back basically the whole file.
Got you!
Yep totally makes sense.
Let's see where it brings us.
I think it has it's use-cases, but so do having the files locally.
Sure thing. Honestly I would love smooth online editing so I can work from private PC without code or tools ever touching my hardware but I'd rather wait couple of more years