4 ms·

I don't really see the appeal. We don't even use the same dev environments at work, some use vscode, others use pycharm or codeblocks or whatever. We have code

I don't really see the appeal. We don't even use the same dev environments at work, some use vscode, others use pycharm or codeblocks or whatever. We have code locally, on github, on gitlab and in other places. Also I can't really say that I've heard anyone outside of this thread who is excited about this at all. I see people here have different ideas but personally I've never heard of it from anyone I work with or know directly.

trumbitta2 3y ago
The issues you listed are non-existent with Gitpod. You can point whatever editor at it, and work on code residing anywhere.
- omgmajk 3y ago
  Good to know but not really for us. Their cloud will not be able to access our internal network where most of our stuff lives. I'm sure it's configurable to some degree but is never going to happen.
  - trumbitta2 3y ago
    https://www.gitpod.io/dedicated https://www.gitpod.io/dedicated
  - ivan_burazin 3y ago
    If you need a selfhosted and managed solution check out our product at https://daytona.io https://daytona.io
deleted 3y ago
[deleted]
SOLAR_FIELDS 3y ago
To me it feels like one of things if executed really well would be amazing, but the first thing that comes to mind when I unwrap it is all of the things that could make it a bad experience. I can also concur that I work in an area a that is doing somewhat bleeding edge infra work (probably second stage adopters) and none of my colleagues or myself is actively seeking out this technology. We don’t really seem to have the problems it purports to solve in a major way at this time.
- AlotOfReading 3y ago
  I'd say it works well enough for maybe 90% of devs at my company. It solves a lot of real issues for them and dramatically simplifies onboarding. The issue is that most of my team are in that 10% and now that 90% of the company have their needs met, we're getting pressure to conform because maintaining all the physical infrastructure for a small group gets expensive. Unfortunately, we can't use cloud environments for a reasonable chunk of our work, so that really means we're get forgotten about until we complain loudly enough, no matter how friendly I am with the relevant teams.

trumbitta2 3y ago

The issues you listed are non-existent with Gitpod. You can point whatever editor at it, and work on code residing anywhere.

omgmajk 3y ago
Good to know but not really for us. Their cloud will not be able to access our internal network where most of our stuff lives. I'm sure it's configurable to some degree but is never going to happen.
- trumbitta2 3y ago
  https://www.gitpod.io/dedicated https://www.gitpod.io/dedicated
- ivan_burazin 3y ago
  If you need a selfhosted and managed solution check out our product at https://daytona.io https://daytona.io

deleted 3y ago

[deleted]

SOLAR_FIELDS 3y ago

To me it feels like one of things if executed really well would be amazing, but the first thing that comes to mind when I unwrap it is all of the things that could make it a bad experience. I can also concur that I work in an area a that is doing somewhat bleeding edge infra work (probably second stage adopters) and none of my colleagues or myself is actively seeking out this technology. We don’t really seem to have the problems it purports to solve in a major way at this time.

AlotOfReading 3y ago
I'd say it works well enough for maybe 90% of devs at my company. It solves a lot of real issues for them and dramatically simplifies onboarding. The issue is that most of my team are in that 10% and now that 90% of the company have their needs met, we're getting pressure to conform because maintaining all the physical infrastructure for a small group gets expensive. Unfortunately, we can't use cloud environments for a reasonable chunk of our work, so that really means we're get forgotten about until we complain loudly enough, no matter how friendly I am with the relevant teams.