typometer
cargo-crev
typometer | cargo-crev | |
---|---|---|
10 | 55 | |
355 | 2,034 | |
- | 1.7% | |
0.0 | 7.7 | |
over 3 years ago | 28 days ago | |
Java | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
typometer
-
Custom-built Emacs vs Pre-built Emacs benchmarks (v30.0.50) and current Emacs performance on Windows
You can download the tool here: https://github.com/pavelfatin/typometer
- Typing latency on wayland
-
Did anyone discover a way to reduce typing latency?
Thanks, that's a really nice offer. Well, if your pi can run typometer that would be an ideal thing to test. Use an editor that has good typing latency. That is nothing based on electron or java. Geany or Kate should work. Don't use vim or emans on a terminal as most terminals have terrible typing latency (except xterm and mlterm)
-
Terminal / Editor benchmarks on 16" M1 Macbook
Typometer with 200 characters
-
Microsoft Dev Box
There is a great comparison between various terminals' latency https://danluu.com/term-latency/ (it comes up periodically on HN too - https://news.ycombinator.com/item?id=19443076), so once when I was curious if it was just me or if RDP was indeed slower, I did a quick test using the same toolset - https://github.com/pavelfatin/typometer
It is not a super-scientific test since:
0) I didn't spend too much time on this
- Ask HN: Is there any tool for benchmarking responsiveness for Linux?
- Popular 'coa' NPM library hijacked to steal user passwords
-
RenderingNG: An architecture that makes and keeps Chrome fast for the long term
open -a Spotify --args --disable-smooth-scrolling
You used to be able to disable Chrome's smooth scrolling with chrome://flags/#disable-smooth-scrolling, but that flag was removed for whatever reason.
I'm also surprised by how much faster Firefox's builtin middle mouse click autoscroll is compared to Chrome's ersatz AutoScroll[2] extension.
[0]: https://download.developer.apple.com/Developer_Tools/Additio...
[1]: https://pavelfatin.com/typometer/
[2]: https://chrome.google.com/webstore/detail/autoscroll/occjjkg...
-
What UI do you use? And why?
First, about the methodology: I took all my measurements with typometer on an Ubuntu 18.04 computer running X11. I tried Firenvim (both in Firefox and Chrome), Fvim, Gnvim, Goneovim, Neovim-Gtk, Nvim-Qt, Nwin and Uivonim. I couldn't try Neovide because it didn't run on my computer. The terminal I tried was Kitty, which has better latency than Alacritty.
-
Neovim slow?
The first thing to do is to try and measure latency to confirm your feeling. You can use something like typometer ( https://github.com/pavelfatin/typometer ) to do that.
cargo-crev
-
Hard disk LEDs and noisy machines
In other cases it may be more documented, such as Golangs baked-in telemetry.
There should be better ways to check these problems. The best I have found so far is Crev https://github.com/crev-dev/crev/. It's most used implementation is Cargo-crev https://github.com/crev-dev/cargo-crev, but hopefully it will become more required to use these types of tools. Certainty and metrics about how many eyes have been on a particular script, and what expertise they have would be a huge win for software.
-
Rust Without Crates.io
The main problem the author is talking about is actually about version updates, which in Maven as well as crates.io is up to each lib's author, and is not curated in any way.
There's no technical solution to that, really. Do you think Nexus Firewall can pick up every exploit, or even most? How confident of that are you, and what data do you have to back that up? I don't have any myself, but would not be surprised at all if "hackers" can easily work around their scanning.
However, I don't have a better approach than using scanning tools like Nexus, or as the author proposes, use a curated library repository like Debian is doing (which hopefully gets enough eyeballs to remain secure) or the https://github.com/crev-dev/cargo-crev project (manually reviewed code) also mentioned. It's interesting that they mention C/C++ just rely on distros providing dynamic libs instead which means you don't even control your dependencies versions, some distro does (how reliable is the distro?)... I wonder if that could work for other languages or if it's just as painful as it looks in the C world.
-
I don't care about cookies” extension bought by Avast, users jump ship
For instance, the worst company imaginable may be in charge of software that was once FOSS, and they may change absolutely nothing about it, so it should be fine. However, if a small update is added that does something bad, you should know about it immediately.
The solution seems to be much more clearly in the realm of things like crev: https://github.com/crev-dev/cargo-crev/
Wherein users can get a clear picture of what dependencies are used in the full chain, and how they have been independently reviewed for security and privacy. That's the real solution for the future. A quick score that is available upon display everytime you upgrade, with large warnings for anything above a certain threshold.
-
I think there should be some type of crates vertification especially the popular ones?
The metrics on crates.io are a useful sniff test, but ultimately you need to review things yourself, or trust some contributors and reviewers. Some projects, like cargo crev or cargo vet can help with the process.
-
[Discussion] What crates would you like to see?
You can use cargo-geiger or cargo-crev to check for whether people you trusted (e.g. u/jonhoo ) trust this crate.
-
Pip and cargo are not the same
There is a similar idea being explored with https://github.com/crev-dev/cargo-crev - you trust a reviewer who reviews crates for trustworthiness, as well as other reviewers.
- greater supply chain attack risk due to large dependency trees?
-
Why so many basic features are not part of the standard library?
[cargo-crev](https://github.com/crev-dev/cargo-crev) looks like a good step in the right direction but not really commonly used.
-
“You meant to install ripgrep”
'cargo crev' makes this kind of workflow possible: https://github.com/crev-dev/cargo-crev
-
Difference between cargo-vet and cargo-crev?
The crev folks themselves are no fans of PGP but need a way to security identify that you are in fact the review author, so that's where the id generation comes in. Ultimately crev is just a bunch of repos with text files you sign with IDs. The nice property is that you can chain these together into a web of trust and it's unfortunate that vet doesn't just use the same signed files on repos model as a foundation because even if they don't trust anyone else, we could turn around and trust them.
What are some alternatives?
feedback - Public feedback discussions for npm
crates.io - The Rust package registry
vim-tmux-navigator - Seamless navigation between tmux panes and vim splits
stackage - Stable Haskell package sets: vetted consistent packages from Hackage
feedback - Public feedback discussions for: GitHub for Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more! [Moved to: https://github.com/github-community/community]
crates.io-index - Registry index for crates.io
zen-kernel - Zen Patched Kernel Sources
serde - Serialization framework for Rust
mpv - 🎥 Command line video player
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project
gpuweb - Where the GPU for the Web work happens!
Rustup - The Rust toolchain installer