Lazydocker direto no host.
Lazydocker direto no host.
Não há fibra em 100% das rotas, ou ela não é prioritária por questão de custo. Ainda utiliza-se links por micro-ondas em certos segmentos, especialmente para interligar cidades pequenas. Há locais que ainda dá para notar degradação na rede durante chuvas intensas.
For programming beginners, definitely. Rust does some abstractions, and when learning, the C pains are a feature.
If there's any fancy modern language that may be a good first start, that's Zig. Unfortunately, it's not released as stable yet, and the documentation and ecosystem are still poor.
Eu só mudaria de distro se estivesse com problemas recorrentes com atualizações ou se outra distro oferecesse alguma vantagem real para meu hardware ou fluxo de trabalho, já que considero que quanto menos personalização inicial for necessário, melhor.
If you can write C++, I'm pretty sure you are smart enough for Rust. You just need to keep pushing until that initial friction is gone.
Here are some awesome materials that can help:
www.youtube.com/watch?v=8-KL...
rust-training.ferrous-systems.com/latest/book/...
Provável que em algum momento tenha sido feito o commit de coisas que não devem ir para o git, tipo a pasta node_modules ou arquivos binários.
É possível reescrever todo o histórico com essa ferramenta. Obviamente, precisa de planejamento para usar na branch principal.
github.com/newren/git-f...
If it's okay for the service to be unavailable at some point (power outage, connection issues, hardware failure), the self-hosted alternative is the most cost-effective unless the power cost in your area is insane.
There are decent and cheap VPS from Hetzner and Contabo, though.
Much better than the glibc hell on Linux.
You can create cross-platform GUIs with C# + AvaloniaUI, Rust + Tauri (using a web stack for the front end), or iced.rs.
I'd first check how good the existing libraries on each ecosystem are to generate the Excel files without messing with COM or WinAPI.
IDE de verdade, só o RustRover, mas ainda é meio bugado.
Já editor, tem bastante: Zed, Lapce, VSCode, Neovim...
I didn't know Cargo allowed that kind of inheritance in the config.
This issue probably arises from the code editors automatically adding dependencies to the nearby Cargo.toml.
Perhaps a custom linting on the CI and/or a pre-commit hook using a custom Taplo schema for the sub-crates will do it.
That looks like an anti-pattern. If there are multiple Cargo.toml files, the top-level one manages the workspace, and it doesn't manage deps, only members and compiler profiles. You can have a single Cargo.toml if it's a flat repo, though.