Tealdeer Alternatives
Similar projects and alternatives to tealdeer
-
-
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
-
updog
Updog is a replacement for Python's SimpleHTTPServer. It allows uploading and downloading via HTTP/S, can set ad hoc SSL certificates and use http basic auth.
-
-
hstr
bash and zsh shell history suggest box - easily view, navigate, search and manage your command history.
-
-
JetBrains
Developer Ecosystem Survey 2022. Take part in the Developer Ecosystem Survey 2022 by JetBrains and get a chance to win a Macbook, a Nvidia graphics card, or other prizes. We’ll create an infographic full of stats, and you’ll get personalized results so you can compare yourself with other developers.
-
-
ytfzf
A posix script to find and watch youtube videos from the terminal. (Without API)
-
-
-
-
-
ripgrep
ripgrep recursively searches directories for a regex pattern while respecting your gitignore
-
-
starship
☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
-
-
glances
Glances an Eye on your system. A top/htop alternative for GNU/Linux, BSD, Mac OS and Windows operating systems.
-
-
tealdeer reviews and mentions
-
I'm new to Linux tell me what's your must have app
check into tldr (my personal favorite implementation is tealdeer and either one should be available on your distro as a package.
- The only Linux command you need to know
- Ffmpeg Buddy
-
A cheatsheet for creating archives with tar, explained.
I prefer tldr, or its faster implementation, tealdeer.
- Hey Devs, what’s your favorite “Cheat Sheet” that you use?
- What are some of your favorite CLI/TUI apps?
- What’s on your arch install?
-
Node.js packages don't deserve your trust
> While I find projects in those other languages to also have too many dependencies, it's no where near what happens in JS apps. I'm thinking of projects I've recently worked on in Rust, PHP, and Java.
My experience with these new languages is such that this feels a bit unfair. It's like insisting that a disaster with 1000 fatalities is "much worse" than one with "only". It's ... true ... I guess, but there's something uncomfortable about making the comparison. Something has gone badly wrong if the comparison even needs to happen in the first place.
What I'm getting at is that e.g. Rust has an enormous problem in this area. It's not uncommon for me to see Node projects with over a thousand transitive dependencies, but on the other hand, I very frequently see Rust projects with over a hundred. And the Node projects tend to be more complicated than the Rust ones; they do more.
Take the last Rust program I tried to use, tealdeer. [1] If you don't know, tldr is a project that provides alternative simplified man pages for commonly used programs that consist entirely of easy to understand examples for the program. [2] What a tldr client needs to do is simply to check a local cache for each lookup, and if necessary update the cache online. It's a trivial problem that can be, and has been! [3], solved in a few hundred lines of shell (if you're being extremely verbose). How many recursive dependencies would you guess tealdeer uses? Depends on how you count, of course, but as of today the answer is ~133 deduplicated dependencies! For a program that's a glorified wrapper around curl!
Or another Rust program I looked at recently, rua [4]. In Arch Linux, the AUR is a repository of user maintained scripts for building and installing software as native Arch packages. Official tools for the building and installing software already exist for Arch, but it is common for users to use a wrapper around these tools that makes fetching and updating the software from the AUR easier. It's a relatively simple task that (once again) can be done with shell scripts. rua is such a wrapper. As of today it uses 137 deduplicated dependencies!
These Rust programs are simple terminal tools to do tasks that are almost trivial in nature. And yet they require hundreds of constantly updating dependencies! The situation may well be better than what you'll find for Node, but it's undeniably disastrous compared to either simpler languages without a built in package manager (like C) or more complicated batteries-included languages where best practices continue to prevail (like Python).
[1] https://github.com/dbrgn/tealdeer
[2] https://tldr.sh/
-
Arch Linux
personally, i like using tealdeer, so check your distro's native packages for it. (you might have a native tldr package, too, but tealdeer is faster) if you can't find tealdeer as a native package, you can always grab the latest release from the project's github page.
-
git is my personal Waterloo
There is also tools like tealdeer that can give you a quick reminder if you forget any specific syntax for the tools you use like git.
-
Git add submodule alternative with offline computer
Hello, I want to share dotfiles between two computers, but one of them is for admin task only (no internet connection, can only manage servers on a private network). For example, I use tealdeer (https://github.com/dbrgn/tealdeer) as quick reminder of command argument, but to work it need internet to collect tldr-pages (https://github.com/tldr-pages/tldr). It stores pages in cache in ~/.cache/tealdeer, so I tried to add this directory on my dotfiles repositories, git give me a hint to use git submodule instead.
-
Urban Dictionary
it is a command line tool primarily, an alternative to the man pages, offering more sane examples of what you might actually do with a cli tool. You can check out the normal tldr-pages here, and the specific client i use here, but there are a number of clients that can be on the web, command line, and in other places
-
"--help", the most useful parameter in GNU/Linux
but, tealdeer, tho. -- https://github.com/dbrgn/tealdeer
- Tealdeer 1.5.0
-
Docopt
I like Docopt for quick scripts, used it both in Python and Rust projects. It is quite unflexible though.
The Rust Docopt implementation¹ was deprecated this year, which is probably good because clap v3 (https://github.com/clap-rs/clap) is so awesome. In a project of mine (tealdeer), I noticed that docopt.rs was responsible for the huge majority of CPU instructions when running the binary: https://github.com/dbrgn/tealdeer/issues/106#issuecomment-59... I then switched² to clap and shaved off almost a megabyte from the release binary³. Performance improved as well, time required for rendering a tldr page went down from ~15.9 ms to ~12.4 ms⁴. With the migration, we also managed to reduce a lot of custom validation logic and move this logic into the derive macro attributes.
Stats
dbrgn/tealdeer is an open source project licensed under Apache License 2.0 which is an OSI approved license.
Popular Comparisons
Are you hiring? Post a new remote job listing for free.