Hope not. I prefer a lot of Desktop apps and prefer them not to be electron based which lately is not possible I assume (unless you build your own). Everyone started rewriting stuff to be electron based - except some IDEs (IDEA based, Visual Studio the no Code one, and some others) which have a potential to change. Even Adobe uses it for some parts (for now I think it's just the Cloud tool for installing stuff) - but it did always run browser engines in the apps like Presto or todat Blink if I'm not mistaking but thats different from a full blown electron based for these cases.
A couple of years back I stumbled upon Apache Che which looks too similar to VS Code so it was in the web for a long time if we're being honest. This is good for companies not wanting the code ever hitting the dev machine avoiding resource problems but then you have network and other things that get you irritated sometimes. Also it's good for not using GIT on multiple machine and not having to do push-pull when you're switching, just when you actually want others to get your changes.
However, I'm still irritated by some of the stuff and browser-based is not for me. Controls, like shortcuts and indipendence of network is much more fluid for me in a non-browser app. Opening large files feels more smooth, like 1GB JSON or XML - it doesn't matter if you shouldn't do it, it still works OK in non electron apps while it studders sometimes in a VS Code and I still need to debug sometimes things like that. Given that I use 16GB on my slowest machine imagine running VS Code on Windows with 8GB and it's a laptop. Your laptop becomes a jet engine. OK, people are using Macs and Linux and have more than 8GB ram today on Windows, and I admit even intellij will make your laptop jet engine sometimes but besides the noise it's aay smoother experience with all the basic plugins I use compared to stuff I need to use with VS Code. Code's great for JS and such things but, formatting, refactoring and code suggestions are way above in full blown IDEs and it works faster
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
To be fair I think habits or being familiar with something (so yes, age) has a lot of impact on many things. But I refuse to believe that's the main reason and sudden boom of JS on desk apps (an general web that replaces desk apps) was more of an alternative to failing local machines and loosing data rather than intended full on replacements. We were at the mainframe stage and now we're getting back there so logical flow would be getting back to local (desk or whatever it's called then). I'm just 31 but I remember big desktop apps doing bunch of serious stuff and they were quite fast, well some of the best ones - there were quite buggy apps as well. But old MS word actually was faster in startup than today's one before 2007 version. I guess we should go back yo C/C++ or continue with Rust. Looking at the whole picture it's apparent that smartphone/tablet apps are the thing while dekstop is getting deprecated for web. I guess once arm or riscv hits desktop well get back to apps
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.
Hope not. I prefer a lot of Desktop apps and prefer them not to be electron based which lately is not possible I assume (unless you build your own). Everyone started rewriting stuff to be electron based - except some IDEs (IDEA based, Visual Studio the no Code one, and some others) which have a potential to change. Even Adobe uses it for some parts (for now I think it's just the Cloud tool for installing stuff) - but it did always run browser engines in the apps like Presto or todat Blink if I'm not mistaking but thats different from a full blown electron based for these cases.
A couple of years back I stumbled upon Apache Che which looks too similar to VS Code so it was in the web for a long time if we're being honest. This is good for companies not wanting the code ever hitting the dev machine avoiding resource problems but then you have network and other things that get you irritated sometimes. Also it's good for not using GIT on multiple machine and not having to do push-pull when you're switching, just when you actually want others to get your changes.
However, I'm still irritated by some of the stuff and browser-based is not for me. Controls, like shortcuts and indipendence of network is much more fluid for me in a non-browser app. Opening large files feels more smooth, like 1GB JSON or XML - it doesn't matter if you shouldn't do it, it still works OK in non electron apps while it studders sometimes in a VS Code and I still need to debug sometimes things like that. Given that I use 16GB on my slowest machine imagine running VS Code on Windows with 8GB and it's a laptop. Your laptop becomes a jet engine. OK, people are using Macs and Linux and have more than 8GB ram today on Windows, and I admit even intellij will make your laptop jet engine sometimes but besides the noise it's aay smoother experience with all the basic plugins I use compared to stuff I need to use with VS Code. Code's great for JS and such things but, formatting, refactoring and code suggestions are way above in full blown IDEs and it works faster
I would argue the online editors make handling large files easier, as they do all the processing for you.
So your hardware device doesn't have to do the heavy lifting.
As for now i'm also more a fan of doing the work locally, mainly because I like to test out what I right directly on testing tools.
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
I hope not either. Not sure if it's an age thing(I'm 44) but I much prefer desktop apps.
To be fair I think habits or being familiar with something (so yes, age) has a lot of impact on many things. But I refuse to believe that's the main reason and sudden boom of JS on desk apps (an general web that replaces desk apps) was more of an alternative to failing local machines and loosing data rather than intended full on replacements. We were at the mainframe stage and now we're getting back there so logical flow would be getting back to local (desk or whatever it's called then). I'm just 31 but I remember big desktop apps doing bunch of serious stuff and they were quite fast, well some of the best ones - there were quite buggy apps as well. But old MS word actually was faster in startup than today's one before 2007 version. I guess we should go back yo C/C++ or continue with Rust. Looking at the whole picture it's apparent that smartphone/tablet apps are the thing while dekstop is getting deprecated for web. I guess once arm or riscv hits desktop well get back to apps