Well, until you realize that VSCode is a Javascript app (packaged with Electron) ... it isn't that much more than a browser app really, and look how performant it is, it's more than adequate for the great majority of development tasks.
Closes eyes and pinches bridge of nose.
You do realize that the Javascript engine in question is written in C++ running natively on the local machine, right? This is no more a "glorified browser app" than Python is. It's an interpreted language, not a website. Javascript just happens to be the language being interpreted.
And yes, I'm aware that Electron is using HTML and CSS for its styling. Once again — files being interpreted. There are other non-Electron, non-JS GUI toolkits that leverage CSS.
Most of the issues with web browser performance has a lot to do with the web browser itself, and with the particular Javascript engine, not the webkit per se. So this is really an apples-and-oranges type issue.
Yes, that Javascript engine is probably written in C/C++, but what's your point then? If you run VSCode on your local machine, then you're effectively running an editor or lightweight IDE in the browser ... and if you'd use a cloud based IDE then you're also running an editor/IDE in the browser ... same, or not?
Well yes okay, the cloud development idea as such assumes that your connection is fast enough, otherwise the whole concept falls flat, so that's a big "if" ... downloading the source code would be one time and then being cached, I suppose.
Except it isn't just the source going over network. It's the data, the response times for operations, etc.
And it isn't just a matter of if your net is fast enough to WORK. It becomes a limiting factor in most cases: the responsiveness of many operations will be limited by network speed, not just local storage IO speed.
Yeah maybe, there's a lot to be said about all this, but this wasn't the original comment of this thread ... :-)
The original comment said that the performance of a desktop application developed in C/C++ would always be superior over a browser based application. To which I responded that VSCode is in fact a browser/JS based app (and some other IDEs are developed in Java rather than C/C++).
So we're having a different discussion now than the original one.
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.
Closes eyes and pinches bridge of nose.
You do realize that the Javascript engine in question is written in C++ running natively on the local machine, right? This is no more a "glorified browser app" than Python is. It's an interpreted language, not a website. Javascript just happens to be the language being interpreted.
And yes, I'm aware that Electron is using HTML and CSS for its styling. Once again — files being interpreted. There are other non-Electron, non-JS GUI toolkits that leverage CSS.
Most of the issues with web browser performance has a lot to do with the web browser itself, and with the particular Javascript engine, not the webkit per se. So this is really an apples-and-oranges type issue.
Electron packs a browser which is not much different to your local chrome + it runs a node process.
With a cloud IDE, you can run expensive tasks on many servers.
That said, Codesphere's goal is not to replace your IDE, its meant to replace your cloud provider.
We aim to do this in the long run with lower prices, more automation, more privacy and no setup.
The UI is an IDE because..uhm..yeah we liked the idea :)
Yes, that Javascript engine is probably written in C/C++, but what's your point then? If you run VSCode on your local machine, then you're effectively running an editor or lightweight IDE in the browser ... and if you'd use a cloud based IDE then you're also running an editor/IDE in the browser ... same, or not?
Uhm....server round trip time? Unless it loads entirely locally, and then you have the initial download time more or less each time.
Network changes everything.
Well yes okay, the cloud development idea as such assumes that your connection is fast enough, otherwise the whole concept falls flat, so that's a big "if" ... downloading the source code would be one time and then being cached, I suppose.
Except it isn't just the source going over network. It's the data, the response times for operations, etc.
And it isn't just a matter of if your net is fast enough to WORK. It becomes a limiting factor in most cases: the responsiveness of many operations will be limited by network speed, not just local storage IO speed.
Ergo "this is apples to oranges".
Yeah maybe, there's a lot to be said about all this, but this wasn't the original comment of this thread ... :-)
The original comment said that the performance of a desktop application developed in C/C++ would always be superior over a browser based application. To which I responded that VSCode is in fact a browser/JS based app (and some other IDEs are developed in Java rather than C/C++).
So we're having a different discussion now than the original one.