projector-docker VS devbox

Although they've basically closed source it since release, Jetbrains Projector was a fantastic tool I've used a lot in the past for that - Just spin up a docker container on my home server and pull out my ipad keyboard

https://github.com/JetBrains/projector-docker

Unfortunately, It's hard to tell if JetBrains Gateway will keep all of the remote dev features or not.

If you have a student package from JB, you can use CLion for Rust development (as do I) and spin up a cloud instance of Clion https://github.com/JetBrains/projector-docker Then you can access it from anywhere over the web.

You can self host Jetbrains IDEs actually! https://github.com/JetBrains/projector-docker

Maybe try using IntelliJ Projector - just run your IntelliJ harmlessly (almost) in the browser :D You can run it simply using docker, run on your machine, or even on the cloud. I have tried to use that for my personal projects and it works.

Worked a lot better using one of their Docker images, but feels like it has too many drawbacks compared to my current VcXsrv setup. Cool stuff though, hope it gets developed further.

How does Flox compare to Devbox? https://github.com/jetpack-io/devbox

I've spent the last year managing all my packages with Devbox (https://github.com/jetpack-io/devbox).

Local dev, cloud dev, CI, production – all with the same config file. Fingers crossed my talk submission for PackagingCon gets accepted. It'd be awesome to share this new way of working with a wider audience.

> Now to figure out what a "flake" is…

Flake is a worthwhile addition to Nix that is worth learning. But like anything Nixian, it's not straightforward.

Have you checked out any of the tools that aim to simplify Nix experience? We built Devbox (https://github.com/jetpack-io/devbox) with this in mind.

Also devbox ( https://github.com/jetpack-io/devbox ) which is what this is for does not work on windows because of its Nix dependency.

For these reasons, I believe most developer environments should prioritize developer experience over fidelity. Tools like Containerized development environments and cloud emulators can strike the right balance and there’s no surprise that we see increased activity around devcontainers, and similar solutions.

Local first, cloud optional is the only way (IMHO) we're going to get people off their local laptop development setups.

We need to support local dev environments first, with the exact same config a developer can then move to the cloud.

See https://github.com/jetpack-io/devbox for how this can be achieved and https://www.mikenikles.com/blog/dev-environments-in-the-clou... for my thoughts after 3 years of working in this space.

If you like the properties of Nix, but find it confusing, you should check out Devbox! It simplifies the process of creating Nix-powered dev environments:

https://github.com/jetpack-io/devbox

As part of the work we've been doing with [devbox](https://github.com/jetpack-io/devbox), we needed a unit testing framework to test some of our nix code. Unfortunately we had some use cases where we did *not* want to introduce a dependency on `nixpkgs` (and therefore we couldn't use `runTests`).

You might be interested in Devbox (http://jetpack.io/devbox)! We built Devbox because we were frustrated with our Docker based dev environments, and our goal is to provide the power of Nix with a more accessible interface (similar to yarn or other package managers).

We're open source and rapidly adding features, you can check us out on Github at https://github.com/jetpack-io/devbox