vscode-remote-release
min-sized-rust
vscode-remote-release | min-sized-rust | |
---|---|---|
35 | 101 | |
3,494 | 7,448 | |
1.2% | - | |
3.0 | 6.2 | |
15 days ago | about 2 months ago | |
Rust | ||
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vscode-remote-release
-
Code tunnel to local machine directly (without Azure)
It would be great, if people interested in this feature/having similar problems would consider pushing the following issue: https://github.com/microsoft/vscode-remote-release/issues/8373
-
xdg-open shim for remote ssh to headless server (VSCode)
The other option may require that you add the Remote X11 extension to VSCode (Unless Microsoft has undone the damage they did to their OpenSSH client in the last few years in which case you could just enable X11 forwarding in your ssh options) if you're trying to execute everything from VSCode, and you would have to have a suitable browser or viewer installed on the remote server along with the xdg-utils package (or whatever contains xdg-open if you're not running Debian).
- Remote VSCode over SSH crashes EC2 instance
-
How to execute a file that sets up the environment that is needed for intelisense to work properly?
Take a look at this: https://github.com/microsoft/vscode-remote-release/issues/6375
-
Host pty got disconnected
If it's "The connection to the terminal's pty host process is unresponsive, the terminals may stop working", apparently it's an old problem: https://github.com/microsoft/vscode-remote-release/issues/7964
- Requesting upvotes for vs code dev container postStartCommand issue
-
A step to step guide to set up Dev Container
VSCode with Remote-Container extension installed.
-
SSH on Raspberry Pi using VS Code
Possibly related github issue?
-
Connect from Visual Studio Code to FreeBSD
This might be it.
-
A way to connect to computers via SSH without VPN
Hello! I came across this Github issue that I think would be helpful for remote workers. It's about the possibility to connect to an existing tunnel by using the terminal of OS instead of VSCode UI. This would allow us to use tunnels as a full SSH replacement in scenarios where SSH itself isn't possible. If you think this would be helpful, please upvote the issue here: https://github.com/microsoft/vscode-remote-release/issues/8238
min-sized-rust
-
The Linux Kernel Prepares for Rust 1.77 Upgrade
This is a good guide on building small Rust binaries: https://github.com/johnthagen/min-sized-rust
This talks about going to extreme lengths on making the smallest Rust binary possible, 400 bytes when it was written, https://darkcoding.net/software/a-very-small-rust-binary-ind...
The thing is, you lose a lot of nice features when you do this, like panic unwinding, debug symbols, stdlib… for kernel and some embedded development it’s definitely important, but for most use cases, does it matter?
-
Rust wont save us, but its ideas will
Oh it was 137, haha. I will link you to this older comment of mine: https://news.ycombinator.com/item?id=29408906
See also https://github.com/johnthagen/min-sized-rust
-
Making Rust binaries smaller by default
Are you sure? If so then this is awesome news, but I'm a bit confused; the commit in that min-sized-rust repo adding `build-std` to the README was merged in August 2021: https://github.com/johnthagen/min-sized-rust/pull/30
Are you saying that at that point the feature still hadn't "landed in Rust nightly" until recently? If so then what's the difference between a feature just being available in Rust nightly, vs having "landed"?
-
Was Rust Worth It?
Rust binaries are by default nowhere close to 500MB. If they are not small enough for you, you can try https://github.com/johnthagen/min-sized-rust. By avoiding the formatting machinery and using `panic_immediate_abort` you can get about the size of C binaries.
-
Compiling Rust binaries for Windows 98 SE and more: a journey
A useful reference: https://github.com/johnthagen/min-sized-rust
- How to minimize Rust binary size
- Error on flashing embedded code to stm32f103
-
Tiny Binaries (2021)
That must be without stripping. Also there are ways to reduce binary size. See e.g. [min-sized-rust](https://github.com/johnthagen/min-sized-rust). I've gotten stripped binaries of small cli utils less than 400KiB without doing anything special, less than 150 KiB by customizing profile settings and compressing with upx, and less than 30 KiB by replacing the std with the libc as the link shows. Haven't tried with fltk though...
-
Shared libraries
This is not quite what you're asking, but it does also address the underlying concern: https://github.com/johnthagen/min-sized-rust
What are some alternatives?
pylance-release - Documentation and issues for Pylance
smartstring - Compact inlined strings for Rust.
rpm-ostree - ⚛📦 Hybrid image/package system with atomic upgrades and package layering
Cargo - The Rust package manager
patchelf - A small utility to modify the dynamic linker and RPATH of ELF executables
rustc_codegen_gcc - libgccjit AOT codegen for rustc
god-mode - Minor mode for God-like command entering
c2rust - Migrate C code to Rust
pyright - Static Type Checker for Python
regex - An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
ostree - Operating system and container binary deployment and upgrades
embedded-graphics - A no_std graphics library for embedded applications