But as soon as the matrix between development environments and projects get bigger, this becomes a huge productivity boost. Of course, if you're just working on one main project, or a few with a shared toolchain, this won't be adding much value for you. And I'm not talking about editor configs, but the entire toolchain. GitPod) is to codify your development environment - similarly to what has been happening in the infrastructure world. The thing that this allows (and the companies that inspired this stuff, e.g. More updates and ideas in the eBPF day recordings from KubeCon EU last week. Potentially interesting for Ops running the remote development platforms (e.g. The limitations can also bring in new views, for example to switch to using time limited tokens instead of plain text auth (Hashicorp Vault, etc.) and evaluate more possible attack vectors, and ways to mitigate and observe security problems.Ī remote development environment runs in a sandbox, similar to a container in CI/CD jobs, can be limited with auth and access, and also be monitored for syscalls and other unexpected behaviour. Fixable in my environment, can become a problem with teams and onboarding at scale. Similar thought with install routines in extensions (and dependencies) that are scanning your local home directory, where Git/cloud/etc. A different way for supply chain attacks, the local dev environment. Worst case - take your source code and, given properly isolated dev env, take only development secrets and data, which must not be useful. > It can benefit security too: no longer can "npm install" consume your private stuff. Working on a remote server over SSH (including pubnix systems), possibly with X forwarding (also similar to the discussed approach, with a thin client, though doesn't require special software).Įdit: also depending on kinds of projects one works on, some of those won't work at all: developing software that interacts with hardware, even something common like a graphics card, may not work at all (or work better, depending on a setup) with remote approaches, and is likely to be more tricky with virtualized ones.Įdit 2: actually looking closer into GitLab Web IDE, seems like it may be closer to the remote/virtual desktop software, but accessible via a web browser. Web-based projects (as being discussed). I've also heard of a person downloading a VM from an online storage, working in it, saving the progress, uploading that - allowing to work locally. (Possibly lightweight) virtualization: used commonly, with all the containerization. Configuration management software (ansible and friends, and/or just git and stow): also rather for advanced users and may require some debugging/adjustments. Being a remote system in a thin client, seems similar to the web IDE approach. Remote (virtual) desktop: network lags, dependence on Internet connection, issues with resolution mismatches and whatnot, but fairly straightforward and seems to be somewhat popular. Nix, Guix, package managers in general: suitable for advanced users, but smooth sailing is not guaranteed, especially with Nix/Guix on top of an arbitrary system. There is a few more approaches to solving this, with different drawbacks: Plus their other product offerings will interface cleanly for even more sales. The first companies to get there will be looking at 10 billion+ TAMs. When HR terminates you, all access instantly goes away. Frontend, backend, marketing, film editing, you name it. Press a button and it builds and executes. All the code, assets, and changes are in one place. You can share them with your coworkers: "Hey, look at my work and check out XYZ". Workspaces can instantly boot up on any machine. Every creative industry is going to undergo this change. It's not just going to be our industry, either. The CTO or CEO will be making this call instead of ICs. > but for me, the lack of control does not outweigh this convenience If a company wants a truly interchangeable workforce, they want standard tools that look the same everywhere. Companies want to focus on their core competency.Īlso, devenv is non-standard across companies. This is a cost center and will be underfunded in most companies and orgs. The ailments you describe can be resolved by having a small dedicated Developer Experience team.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |