Potential of browser based IDEs
-
I was looking at Ares - a web based IDE for Palm Pre development. I must say that I am impressed. The IDE is pretty responsive and lot of features you expect in a desktop IDE are present in Ares. Of course, I have not done any real work to see how the IDE will hold up. But it seems to be a nice start. So do you expect to see a Browser based (most likely SilverLight) version of VS2010? (may be something which is lower than the Express edition in the hierarchy). The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
-
I was looking at Ares - a web based IDE for Palm Pre development. I must say that I am impressed. The IDE is pretty responsive and lot of features you expect in a desktop IDE are present in Ares. Of course, I have not done any real work to see how the IDE will hold up. But it seems to be a nice start. So do you expect to see a Browser based (most likely SilverLight) version of VS2010? (may be something which is lower than the Express edition in the hierarchy). The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
-
I was looking at Ares - a web based IDE for Palm Pre development. I must say that I am impressed. The IDE is pretty responsive and lot of features you expect in a desktop IDE are present in Ares. Of course, I have not done any real work to see how the IDE will hold up. But it seems to be a nice start. So do you expect to see a Browser based (most likely SilverLight) version of VS2010? (may be something which is lower than the Express edition in the hierarchy). The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
I've only seen one that did .Net. Damned if i can remember the site now. There was a lot of neato factor that you could do it on the web. Not installing a dev machine is great. But it lacked all the bells and whistles visual studio provided so doing serious development would be a challenge. UPDATE: Figures that soon as I post I found the site again. http://www.coderun.com/ide/[^]
-
I was looking at Ares - a web based IDE for Palm Pre development. I must say that I am impressed. The IDE is pretty responsive and lot of features you expect in a desktop IDE are present in Ares. Of course, I have not done any real work to see how the IDE will hold up. But it seems to be a nice start. So do you expect to see a Browser based (most likely SilverLight) version of VS2010? (may be something which is lower than the Express edition in the hierarchy). The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
-
ideal for creating vaporware... :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
Prolific encyclopedia fixture proof-reader browser patron addict?
We all depend on the beast below.
-
I was looking at Ares - a web based IDE for Palm Pre development. I must say that I am impressed. The IDE is pretty responsive and lot of features you expect in a desktop IDE are present in Ares. Of course, I have not done any real work to see how the IDE will hold up. But it seems to be a nice start. So do you expect to see a Browser based (most likely SilverLight) version of VS2010? (may be something which is lower than the Express edition in the hierarchy). The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
-
ideal for creating vaporware... :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
Prolific encyclopedia fixture proof-reader browser patron addict?
We all depend on the beast below.
You totally just stole my thunder :rolleyes:
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL -
-
I was looking at Ares - a web based IDE for Palm Pre development. I must say that I am impressed. The IDE is pretty responsive and lot of features you expect in a desktop IDE are present in Ares. Of course, I have not done any real work to see how the IDE will hold up. But it seems to be a nice start. So do you expect to see a Browser based (most likely SilverLight) version of VS2010? (may be something which is lower than the Express edition in the hierarchy). The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
Rama Krishna Vavilala wrote:
So do you expect to see a Browser based (most likely SilverLight) version of VS2010?
No, but I wouldn't be surprised to see MS throw out a light-weight Silverlight IDE at some point. The tricky part is going to be the debugger - Ares hooks into the (locally-installed) SDK using Java, with the program running either in an emulator (VirtualBox) or on an actual device; while Silverlight could do something similar (which version has COM support?) i suspect the current debugging APIs won't support it without considerable effort (.NET debugging is a strange beast). A Silverlight IDE for Silverlight apps could probably happen though (if the independent Silverlight runtime is more accommodating of such extensions).
-
You totally just stole my thunder :rolleyes:
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTLsorry about that, seems I'm growing a bad habit[^] then. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
Prolific encyclopedia fixture proof-reader browser patron addict?
We all depend on the beast below.
-
I was looking at Ares - a web based IDE for Palm Pre development. I must say that I am impressed. The IDE is pretty responsive and lot of features you expect in a desktop IDE are present in Ares. Of course, I have not done any real work to see how the IDE will hold up. But it seems to be a nice start. So do you expect to see a Browser based (most likely SilverLight) version of VS2010? (may be something which is lower than the Express edition in the hierarchy). The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
They got the e and the s the wrong way around...
-
I was looking at Ares - a web based IDE for Palm Pre development. I must say that I am impressed. The IDE is pretty responsive and lot of features you expect in a desktop IDE are present in Ares. Of course, I have not done any real work to see how the IDE will hold up. But it seems to be a nice start. So do you expect to see a Browser based (most likely SilverLight) version of VS2010? (may be something which is lower than the Express edition in the hierarchy). The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
Rama Krishna Vavilala wrote:
The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
Actually, that's a HUGE disadvantage, IMHO. I don't want the damn IDE changing on me in the middle of an intense project development cycle. Maybe it's just me, but I like stability and the delusion of control. I turn off automatic updates, because I'll decide when and if I want to update the apps I use. And as to a browser-based IDE, I'm sorry, but I still frequently enough work in a disconnected state that I don't want anything important to be living on the web, be it data or tools. And even in a theoretical "always connected" scenario, I don't want to deal with the downtime of the inevitable hardware failure, routers, cable/DSL modems, drunk drivers smashing into telephone polls, lightning strikes and other acts of God, etc. In other words, I'd be happy living in a cabin on a remote mountain with a once-a-day 10 minute data burst as a satellite passes overhead. The rest of the time, I could easily live without an Internet connection. Marc
-
Rama Krishna Vavilala wrote:
The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
Actually, that's a HUGE disadvantage, IMHO. I don't want the damn IDE changing on me in the middle of an intense project development cycle. Maybe it's just me, but I like stability and the delusion of control. I turn off automatic updates, because I'll decide when and if I want to update the apps I use. And as to a browser-based IDE, I'm sorry, but I still frequently enough work in a disconnected state that I don't want anything important to be living on the web, be it data or tools. And even in a theoretical "always connected" scenario, I don't want to deal with the downtime of the inevitable hardware failure, routers, cable/DSL modems, drunk drivers smashing into telephone polls, lightning strikes and other acts of God, etc. In other words, I'd be happy living in a cabin on a remote mountain with a once-a-day 10 minute data burst as a satellite passes overhead. The rest of the time, I could easily live without an Internet connection. Marc
On the other hand, I will like the following:- 1. Ability to access the source code from anywhere. May be (if it works) even ability to debug on client machines without installing anything. 2. Backup automatically managed on the cloud. As it stands, most of the cloud apps now do use offline data storage which is a part of HTML 5 (also supported by SilverLight). As with everything there are pros and cons and one need to individually weigh them for their own special needs.
-
On the other hand, I will like the following:- 1. Ability to access the source code from anywhere. May be (if it works) even ability to debug on client machines without installing anything. 2. Backup automatically managed on the cloud. As it stands, most of the cloud apps now do use offline data storage which is a part of HTML 5 (also supported by SilverLight). As with everything there are pros and cons and one need to individually weigh them for their own special needs.
Rama Krishna Vavilala wrote:
Ability to access the source code from anywhere.
Which I can do easily from my server and through SVN.
Rama Krishna Vavilala wrote:
May be (if it works) even ability to debug on client machines without installing anything.
Which would be impossible, given the security that's involved in the location of information.
Rama Krishna Vavilala wrote:
Backup automatically managed on the cloud.
Security policy issues, and also I can do backups from my server to my machine, no wondering what hands my backups are falling into.
Rama Krishna Vavilala wrote:
most of the cloud apps now do use offline data storage which is a part of HTML 5 (also supported by SilverLight).
Ah, that's cool. :) Barring my "I want total control to do things my way" attitude, there obviously a huge market for cloud computing, some definite benefits to specific users, etc. But I also think cloud computing is sort of looking for a problem to solve. In some cases, cloud computing solves a problem people already have, in other ways (like mine) it's (as much as a concept can do this) trying to force me to change my work paradigm to fit the technology capabilities. Whenever I see that, I pretty much run, as that's rather the opposite of what technology should be doing. Marc
-
Rama Krishna Vavilala wrote:
The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
Actually, that's a HUGE disadvantage, IMHO. I don't want the damn IDE changing on me in the middle of an intense project development cycle. Maybe it's just me, but I like stability and the delusion of control. I turn off automatic updates, because I'll decide when and if I want to update the apps I use. And as to a browser-based IDE, I'm sorry, but I still frequently enough work in a disconnected state that I don't want anything important to be living on the web, be it data or tools. And even in a theoretical "always connected" scenario, I don't want to deal with the downtime of the inevitable hardware failure, routers, cable/DSL modems, drunk drivers smashing into telephone polls, lightning strikes and other acts of God, etc. In other words, I'd be happy living in a cabin on a remote mountain with a once-a-day 10 minute data burst as a satellite passes overhead. The rest of the time, I could easily live without an Internet connection. Marc
Pretty sure I've talked about this before, but... There's one huge potential advantage for a "cloud-based" IDE (whether browser-based or otherwise): integrated source control. Yeah, I know. I hate it too. ;-) But I hate it because it gets in my way. I don't really ever want to see source control when I'm writing, any more than I want someone standing over my shoulder talking about the movie watched last night. But when I'm editing, or trying to track down the source of a problem, it could be useful... Flag routines that someone else is working on so I can coordinate with them, integrate "blame/annotate" so I can quickly identify the author and origin of each change, let me pick a specific revision to test against... ...and of course, that's all possible now, using most modern source controls systems. But they're slow. They get in my way. They require me to be involved in the fiddly details of maintaining the local cache, er, "working directory". Example: creating a new branch is fast, but pulling down the files for that branch into a separate local working area is slow... Never mind that most of the files are already on my machine, unchanged and unlikely to change. The solution is to give up on the idea that you're editing local files. Your IDE (editor, compiler, debugger) pull them off the network and cache them locally, but changes belong to a branch somewhere; saving commits it, and you merge up when finished. The local filesystem is a cache, with no need for multiple copies of the same revision of a file. And at that point, an editor in a native-code IDE and an editor in a browser-based IDE are both pulling the file from the same place, both saving changes to the same place, and the choice between them can be made on convenience vs. capability.
-
Pretty sure I've talked about this before, but... There's one huge potential advantage for a "cloud-based" IDE (whether browser-based or otherwise): integrated source control. Yeah, I know. I hate it too. ;-) But I hate it because it gets in my way. I don't really ever want to see source control when I'm writing, any more than I want someone standing over my shoulder talking about the movie watched last night. But when I'm editing, or trying to track down the source of a problem, it could be useful... Flag routines that someone else is working on so I can coordinate with them, integrate "blame/annotate" so I can quickly identify the author and origin of each change, let me pick a specific revision to test against... ...and of course, that's all possible now, using most modern source controls systems. But they're slow. They get in my way. They require me to be involved in the fiddly details of maintaining the local cache, er, "working directory". Example: creating a new branch is fast, but pulling down the files for that branch into a separate local working area is slow... Never mind that most of the files are already on my machine, unchanged and unlikely to change. The solution is to give up on the idea that you're editing local files. Your IDE (editor, compiler, debugger) pull them off the network and cache them locally, but changes belong to a branch somewhere; saving commits it, and you merge up when finished. The local filesystem is a cache, with no need for multiple copies of the same revision of a file. And at that point, an editor in a native-code IDE and an editor in a browser-based IDE are both pulling the file from the same place, both saving changes to the same place, and the choice between them can be made on convenience vs. capability.
Shog9 wrote:
Your IDE (editor, compiler, debugger) pull them off the network and cache them locally
Makes sense, and sounds wonderful, but the very reason that checking out a "working directory" is slow is because my network connection is still about 1,000 times slower than it needs to be, for anything on the Internet to not feel like it's getting in my way. :) Marc
-
Shog9 wrote:
Your IDE (editor, compiler, debugger) pull them off the network and cache them locally
Makes sense, and sounds wonderful, but the very reason that checking out a "working directory" is slow is because my network connection is still about 1,000 times slower than it needs to be, for anything on the Internet to not feel like it's getting in my way. :) Marc
Well, there's where the browser client might have an edge: a single source file should transfer (gzip compressed) fairly quickly (<1sec). Assuming the server-side takes care of handling class browser, Intellisense-type stuff, I'll probably never pull down enough code during a typical editing session to notice... Vs. the tens or hundreds of MB I currently need to pull down to get full support from VS (and that's not counting the time VS takes to rebuild its internal databases every time, for every branch for every user working on that branch...)
-
Rama Krishna Vavilala wrote:
The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
Actually, that's a HUGE disadvantage, IMHO. I don't want the damn IDE changing on me in the middle of an intense project development cycle. Maybe it's just me, but I like stability and the delusion of control. I turn off automatic updates, because I'll decide when and if I want to update the apps I use. And as to a browser-based IDE, I'm sorry, but I still frequently enough work in a disconnected state that I don't want anything important to be living on the web, be it data or tools. And even in a theoretical "always connected" scenario, I don't want to deal with the downtime of the inevitable hardware failure, routers, cable/DSL modems, drunk drivers smashing into telephone polls, lightning strikes and other acts of God, etc. In other words, I'd be happy living in a cabin on a remote mountain with a once-a-day 10 minute data burst as a satellite passes overhead. The rest of the time, I could easily live without an Internet connection. Marc
Marc, I'm a pretty forward thinking EE and techie (the two go together). I too just don't get the cloud. Too much loss of control over apps and data. I guess they figure if you rename the technology enough times someone will eventually buy into it. thin client->saas->cloud longhorn->vista->mojave experiment etc. Now hosting an in-house private cloud -- I can see a business case made there.
-Sean ---- Fire Nuts
-
Marc, I'm a pretty forward thinking EE and techie (the two go together). I too just don't get the cloud. Too much loss of control over apps and data. I guess they figure if you rename the technology enough times someone will eventually buy into it. thin client->saas->cloud longhorn->vista->mojave experiment etc. Now hosting an in-house private cloud -- I can see a business case made there.
-Sean ---- Fire Nuts
Sean Cundiff wrote:
Now hosting an in-house private cloud
Quick! We need to capitalize on that idea. There are obviously different kinds of clouds: Cirrus Cumulus Stratus Stratocumulus NimboStratus Cumulonimbus ... The variety is astounding! We can use the cloud metaphor to describe any network topology!!! And best of all, we can create a whole series of vaporware products!!! Marc
-
I was looking at Ares - a web based IDE for Palm Pre development. I must say that I am impressed. The IDE is pretty responsive and lot of features you expect in a desktop IDE are present in Ares. Of course, I have not done any real work to see how the IDE will hold up. But it seems to be a nice start. So do you expect to see a Browser based (most likely SilverLight) version of VS2010? (may be something which is lower than the Express edition in the hierarchy). The big advantage is that you do not have to mess up your development machine each time there is a new version of IDE or wait for hours for installation of IDE to complete.
There are already enough things that slow down the work -- memory and disc bloat, badly organised threading and priorities within the IDE, etc. Why on Earth would you want to add another layer -- nay, several more layers -- of things that can slow you down and/or screw up your work? Tip: If someone in IT says "This can be done!" and they sound even vaguely excited about it, run a mile.
I wanna be a eunuchs developer! Pass me a bread knife!