3 ms·
> Toolchain integration can be daunting. You need to set up Rust in development builds, production builds, local testing, continuous integration, and so on. Im
by rob74 5y ago
> Toolchain integration can be daunting. You need to set up Rust in development builds, production builds, local testing, continuous integration, and so on.
Impressive that someone familiar with the usual JS development toolchains can write this and keep a straight face...
- deleted 5y ago[deleted]
- janpaul123 5y agoYou didn't see my face when I wrote that ;)
- deleted 5y ago[deleted]
- emteycz 5y agoWhat's so hard about JS toolchain? yarn create next-app --typescript ... and I am done
- girvo 5y agoFor me it’s the same yarn create react-app my-app --template typescript
- edgyquant 5y agoNow include installing node/npm initially and setting that app up for CI/CD
- emteycz 5y agoSure: FROM node:16 Done (including dev env with VSCode dev containers). And if you created a Next app as I suggested, your CI config is super-easy - you need to place 3 commands into your YAML and that's it: yarn lint yarn build yarn start
- edgyquant 5y agoI feel like using docker is cheating as you could do that with Rust as well
- emteycz 5y agoBut can I? I haven't tried recently, but when I tried to setup a dev container for Rust last year I had to do the setup by hand on a raw Ubuntu image. Anyways, cargo and rustup are cool tools, I don't want to criticize Rust. I just don't think the JS tooling is so outlandish as people make it seem so.
- cjg 5y agohttps://hub.docker.com/_/rust https://hub.docker.com/_/rust