4 ms·

"I don't get it." </Tom Hanks, in Big> There's no stack I work in for which a single program is enough to get things done, even if it's a giant, bloated IDE li

"I don't get it." </Tom Hanks, in Big> There's no stack I work in for which a single program is enough to get things done, even if it's a giant, bloated IDE like Visual Studio, IntelliJ, or RubyMine. When I need to operate on the outputs of the IDE, how am I supposed to use my other tools with those files, when they're locked up in a cloud service without a filesystem? Maybe this works for a pull-request review and merge, but I can't see it being useful for any more than that.

neogodless 7y ago
Could you expand upon your tools and workflow a bit? It's not that I disagree with you, at least not for your use cases! But it's not hard for me to think of cases where this would work. First, a quick anecdote - I run a dirt cheap, crummy Windows server at home for pet projects. I've been doing this for well over a decade. Maybe two? Along the way, I wrote a basic web interface for editing files on the server. Basic upload, rename/move, edit text files kind of thing. For pet projects, I work on them infrequently, but sometimes an idea will strike me, or I become aware of a bug or typo, and I just want to get in and fix the issue. Now, these were simpler times - the most complex code was classic ASP or JavaScript! The toolchain was non-existent. A use case for pet projects would be cloud-hosted, cloud-repository, cloud-pipeline, and now cloud-development. When an idea strikes you, rather than pull things locally, configure them for that particular project, with that peculiar set of frameworks and toolchains, you can load up your cloud IDE which is already configured to point to the repository, build and test in a container, deploy through a pipeline to the cloud host, and just focus on making the edits you want without all the work of getting things local. As someone who spent a few hours the other morning working on a computer I don't usually work on just getting the git credentials and containers and runtimes working before I could start getting any work done, I could definitely see a use case for this cloud-based development paradigm.
- therealx 7y ago
  I build a Windows Service which reports to a SaaS. As-is, I have to uninstall the app and use a lot of specific tooling if I want to test a larger change and not go through a bunch of joops. I don't think I'm a good use case for VS web beside maybe fixing a typo in my repo while I'm on the go. Years ago, I'd have called myself a dying breed, but I don't think thats true,
phillipcarter 7y ago
> without a filesystem This might be a bit of an assumption :)
jedieaston 7y ago
You get a Linux (with windows "soon") box in your environment, and all of your code comes in to it and is executed there. You have root. What tools can you not run from within the container? (especially considering that if you really needed to, you could set your local workstation as another environment and move files in between, although at that point why do you need a online IDE (except for conf. management).

neogodless 7y ago

Could you expand upon your tools and workflow a bit? It's not that I disagree with you, at least not for your use cases! But it's not hard for me to think of cases where this would work. First, a quick anecdote - I run a dirt cheap, crummy Windows server at home for pet projects. I've been doing this for well over a decade. Maybe two? Along the way, I wrote a basic web interface for editing files on the server. Basic upload, rename/move, edit text files kind of thing. For pet projects, I work on them infrequently, but sometimes an idea will strike me, or I become aware of a bug or typo, and I just want to get in and fix the issue. Now, these were simpler times - the most complex code was classic ASP or JavaScript! The toolchain was non-existent. A use case for pet projects would be cloud-hosted, cloud-repository, cloud-pipeline, and now cloud-development. When an idea strikes you, rather than pull things locally, configure them for that particular project, with that peculiar set of frameworks and toolchains, you can load up your cloud IDE which is already configured to point to the repository, build and test in a container, deploy through a pipeline to the cloud host, and just focus on making the edits you want without all the work of getting things local. As someone who spent a few hours the other morning working on a computer I don't usually work on just getting the git credentials and containers and runtimes working before I could start getting any work done, I could definitely see a use case for this cloud-based development paradigm.

therealx 7y ago
I build a Windows Service which reports to a SaaS. As-is, I have to uninstall the app and use a lot of specific tooling if I want to test a larger change and not go through a bunch of joops. I don't think I'm a good use case for VS web beside maybe fixing a typo in my repo while I'm on the go. Years ago, I'd have called myself a dying breed, but I don't think thats true,

phillipcarter 7y ago

> without a filesystem This might be a bit of an assumption :)

jedieaston 7y ago

You get a Linux (with windows "soon") box in your environment, and all of your code comes in to it and is executed there. You have root. What tools can you not run from within the container? (especially considering that if you really needed to, you could set your local workstation as another environment and move files in between, although at that point why do you need a online IDE (except for conf. management).