[HN Gopher] Introducing Rust Support in CodeSandbox, start a Rus...
___________________________________________________________________
Introducing Rust Support in CodeSandbox, start a Rust VM in one
click
Author : CompuIves
Score : 46 points
Date : 2023-01-19 19:01 UTC (4 hours ago)
(HTM) web link (codesandbox.io)
(TXT) w3m dump (codesandbox.io)
| revskill wrote:
| I'm hoping Codesandbox would provide for CI/CD to directly deploy
| to production somehow. Basically, it's a "code in cloud" dream.
| CaveTech wrote:
| It's easy enough to add additional actions, so you could pair
| it with netlify, vercel, etc.
| revskill wrote:
| Ease and how long to do it is orthogonal i think.
| CompuIves wrote:
| Yep that works, you can either create a task in the editor
| for it (using the CLI), or you connect it to a GitHub Repo
| and install actions.
|
| That said, it is something on our radar, being able to press
| a button for deploy from CodeSandbox would be valuable for
| many people!
| sigmonsays wrote:
| How many developers are there who are happy using some web based
| IDE versus their own tools?
|
| I'd prefer having my own dev tools maintained locally by me but
| i'm curious if i'm becoming the minority
| lhnz wrote:
| I tend to prefer this way of working when I am doing a demo for
| my team or write the beginning of an open-source hack.
| pictur wrote:
| I started using it while developing on a site running on
| nextjs. It works pretty fast and I can get things done faster.
| There are minor issues, of course, but in its current state it
| works just fine.
| slaymaker1907 wrote:
| I like it when I want to test something out quickly so setting
| up a full dev environment isn't worth the effort.
| flashgordon wrote:
| +1 - Personally not a fan of cloud IDEs - I am ok if the front-
| end for the tool itself is html based but run by/on a local
| http/websocket server. Having to maintain my entire stack on
| the cloud somewhere is something I still havent gotten
| comfortable (yes we use Github for source control _somewhere_
| and cloud for running you stuff _somewhere_ ). Then again I
| didnt _get_ containers 15 years ago!
| CompuIves wrote:
| I'm using a web based IDE for my dev, but I'm biased in that
| sense. The main advantage for me is that I can easily switch
| branches, as every branch has its own VM. + I can easily share
| in-progress work. I do use the VSCode integration, because I'm
| very used to VSCode.
|
| That said, I've also spoken with people who use a Web IDE next
| to their local environment. E.g. they use a Web IDE for
| reviewing PRs or making smaller changes, and they use their
| local editor for feature development.
| Ankhers wrote:
| If this is just for being able to easily switch branches,
| have you considered using git worktrees? Essentially you have
| have multiple branches checked out into different directories
| at the same time. The key point though is that all git refs
| are still maintained in a single place so you are not
| actually having full clones for each worktree that you have.
|
| I personally use Emacs and magit which has great support for
| worktrees. I do not know if the VSCode git integration
| supports it.
| CompuIves wrote:
| Ah right, the main advantage I have here is that the dev
| server also stays running when I go to another branch
| (since it's a different VM). So I can work on one thing,
| share it with the team and in the meantime continue on
| another branch. They can see the devserver / running code,
| while I am working on something else.
|
| It's especially useful for things like migrations or
| dependency management. In one branch I could work on
| something that has some database migrations, and then I can
| still switch to other branches without having to roll back
| the migrations.
|
| I didn't know about git worktrees though! I'm going to read
| up on this.
| faitswulff wrote:
| > In one branch I could work on something that has some
| database migrations, and then I can still switch to other
| branches without having to roll back the migrations.
|
| I would love to have this workflow locally.
| slaymaker1907 wrote:
| I use it with VS Code since the project I work on takes
| 5-10 minutes to build if a major header is modified. It
| shows up as a separate directory, but VS Code will still
| realize that the directory is a git worktree.
|
| The only thing kind of clunky is that you have to keep
| track of which branch is open in which directory since you
| can't checkout the same branch in two different
| directories.
| CompuIves wrote:
| Hey all! I'm one of the co-founders of CodeSandbox and a big fan
| of Rust. Rust support is something that we've been working on for
| a while, but the recent addition of Docker support in CodeSandbox
| really enabled it. Happy to answer any questions!
| MuffinFlavored wrote:
| Is your biggest competitor Repl.it? What advantages do you have
| compared to them?
|
| I know https://play.rust-lang.org/ is pretty limited as well.
| CompuIves wrote:
| Yeah Repl.it is one of the bigger ones.
|
| I'd say that CodeSandbox has a strong focus on extending the
| existing workflow for developers. That's why we have a VSCode
| integration, a GitHub integration with a GitHub App that
| creates a running dev env for every branch/PR, and we make
| sure that generally all editor features you expect
| (autocomplete, go to definition, hover info, etc) are
| available for the languages that we support.
| MuffinFlavored wrote:
| Are you basically reselling hosted
| https://github.com/coder/code-server?
| CompuIves wrote:
| No, we've built our own web editor & iOS code editor. In
| our v1 editor we did run VSCode in the browser, but that
| was before code-server was released (in 2018). Even if we
| wanted to run code-server, that would be impossible as we
| allow for multiple users to open the same sandbox/branch,
| which wouldn't fit the model of VSCode server (which is
| single user per server).
| kylecarbs wrote:
| They aren't at all (creator of code-server here)! I'm a
| big fan of their work.
| terpimost wrote:
| I recently tried to work on CodeSandbox. Simple examples didn't
| work or I couldn't figure out how to make them work. Using
| repl.it now. I highly recommend to go through basic examples of
| frontend projects and evaluate them.
| kodah wrote:
| I'm not really a fan of in-browser IDEs. To me, it seems like a
| good way to constrain tooling environments.
|
| What I would love to see is an extension that runs all of my
| tests and debugger in a type 1 hypervisor that can simply send a
| set of instructions to setup the VM, a snapshot of the changeset,
| and allows a developer to run that exact environment on their
| machine. Combine that with LiveShare and you have something that
| closely mimicks the experience of handing a keyboard and mouse
| back and forth during pairing.
___________________________________________________________________
(page generated 2023-01-19 23:02 UTC)