![]() Just to mention an old-school "secure sandboxed" development environmet: javascript in the browser. The first line of defense should always be to develop in a sandboxed environment. For example: "2022 - Famous npm package 'node-ipc' deletes files on developer machine." And every library is made up of tens of other libraries.Īnytime can happen that an update injects something really malevolent in an obscure non-important library. You will miss most of the interesting libraries. And they also have the money to review the code prior to publishing.īut in open-source it is impossible to work only with "reputable" developers. No company wants to be destroyed financially because of malware in the supply chain. Reputation does exist in the commercial world. Sure there are bugs, incredible incompetence, complete indifference, but there is no malevolent intention.Īlso for third-party libraries sold for money, it is in their best interest to be trustworthy. When you buy stuff for money, you know that there exists some "quality control" behind the product. I worked professionally 30 years with Microsoft "languages". The container steals a little of performance for itself, but it is not a big deal in that combination. That is a big difference! I decided I will develop Rust projects in Debian (dual boot) without shared volume with mold linker. That's ok for me.Ħ.84s in container on WSL2 without shared volumeĥ.05s in container on WSL2 with shared volumeĤ.43s in container on Debian (dual boot) without shared volumeĥ.35s in container on Debian (dual boot) with shared volume The "mold" linker is experimental Linux only. Then I changed the linker to "mold" on Debian. I build a few times and find an average.ġ8s in container on WSL2 without shared volumeĨs in container on WSL2 with shared volumeġ1s in container on Debian (dual boot) without shared volumeħs in container on Debian (dual boot) with shared volume ![]() I tried cargo auto build on my project database_web_ui_on_server in different environments. I wrote my experience using Podman, Buildah, VSCode, Win10, WSL2 and the Official Rust docker image to prepare images and containers for Rust projects.Īfter using these containers for some time I was curious about compile performance in various environments. I want to develop Rust projects in a sandboxed/isolated environment. I am afraid of build.rs and procedural macros and rust development tools that can do "anything" on my system. Rust: Hack Without Fear and Trust! A complete development environment for Rust with VSCode inside a docker container.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |