@sirber @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn
Nah, even when I have a good wireless, optical mouse in front of me, #CommandLine is #BAE. XD
@sirber @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn
Nah, even when I have a good wireless, optical mouse in front of me, #CommandLine is #BAE. XD
New #blog post: Why I Love the Command Line
https://rldane.space/why-i-love-the-command-line.html
1081 words
I was grappling with a much heavier subject for a blost, but thankfully, I had this extra little subject in my back pocket, just ready to be picked up and written on much more easily and enjoyably than mental health stuff. ;)
cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn
(I will happily add/remove you from the chorus upon request! :)
Tachyonfx brings web-level animations to the command line..
Then Ratzilla puts it back in browsers where it belongs
Witness this beautiful chaos: https://junkdog.github.io/exabind
Powered by Rust & @ratatui_rs ecosystem
GitHub: https://github.com/junkdog/exabind
Google gets its swag back https://thever.ge/CqoS #CommandLine #Analysis #Google #Meta #Tech #AI
The power of LibreOffice
I have many documents created with Microsoft Office for assignments written for graduate school courses years ago. How can I easily convert those dozens of documents to a different format without using an online application? This is an excellent example of the power of open source.
Five years ago I took a course at a local university where all of the documents were provided in ‘docx’ format. Is there a way to convert those documents to an ‘odt’ format? There is and it is quite simple.
$libreoffice --headless --convert-to odt *.docx
What if I decided I wanted to convert those ‘docx’ items to ‘html’ so they could easily be shared on my classroom website. What if I had wanted to convert all those documents to html?
$libreoffice --headless --convert-to html *.docx
I can use the same tool to turn those ‘docx’ files into ‘pdf’ files with an iteration of the same command.
$libreoffice –headless –convert-to pdf *.docx
Using LibreOffice from the command line inside the directory where the files you want to convert is easy and the conversion is accomplished in a matter of seconds depending on your processor and memory. You can find many more uses of LibreOffice from the command line by entering the following command on your own command line if you have LibreOffice installed as most Linux distributions do.
$libreoffice --help
This is a great example of the power of open source software.
Have you ever wanted to lint markdown... fast?
**mado** — A Markdown linter written in Rust
Compatible with CommonMark and GitHub Flavored Markdown (GFM).
Approx. 49-60x faster than existing linters
GitHub: https://github.com/akiomik/mado
In fairness, that's a culture that the GNOME, KDE, et al. desktop people changed by doing, years ago.
They've had long meaningful names, with more than 1 vowel in, in the desktop applications world for years.
When it comes to nomenclature "st" actually sucks *more* as a name to unfamiliar users than "gnome-terminal". (-:
It's the same sort of deal with the "convenience" aliases versus the full cmdlet names in #PowerShell.
@Birk_lab There are suitable #Linux replacements for practically any #Microsoft package. Most VM use cases are for gaming and some CAD software. The user friendly Linux distros have them pre installed. For moving files, I'm not sure what you mean. Permissions are by design so you don't nuke your distro. They are easily manipulated thru the #commandline and require very little research. Although some popular Linux distros allow it thru their file managers.
I found a cool collection of Neovim plugins
**snacks.nvim** — Small quality of life plugins for smooth UX, better visuals and smart defaults.
Supports extensive configuration.
I had a dream last night I was the host of a popular YouTube show which was basically Cribs, but for famous programmers showing me around their command line shell setup.
The Linus Torvalds episode did numbers, but no one wanted to watch me show myself around my own shell.
such is the fickle imaginary audience of one's own dreams. Lol.
Azure Developer CLI: From Dev to Prod with One Click.
https://devblogs.microsoft.com/devops/azure-developer-cli-from-dev-to-prod-with-one-click/
The Reworked Terminal Becomes the Default in JetBrains 2025.2.
https://blog.jetbrains.com/platform/2025/07/the-reworked-terminal-becomes-the-default-in-2025-2/
Finally I can preview my PCBs in the terminal
terminal3d — View 3D obj files in the terminal.
Support using mouse controls & different render modes.
Written in Rust!
This post was inspired by the accessibility, or lack there of, of various operating systems, annoyances that people have with Windows, and the current state of Linux, which many sighted people tout as a great Windows alternative. While there are obviously some blind people who use it, overall, the experience is neither streamlined nor easy. and it can be downright frustrating. There is Mac OS, but then, there is the expense of a Mac, plus the fact that many normal periferals can't be used with it. There are Android and IOS, but these are touch-based, not built for computers, though both can be used with real keyboards. Still, such operating systems come with their own headaches.
My solution is one that cuts through all of the hurdles to a system that is fast, efficient, light on resources, and very accessible. This is DOS. I am not referring to MS-DOS, but to modern varients such as FreeDOS (just updated this year), Enhanced DR-DOS (updated a few years ago), VDOS (a version that runs directly in modern Windows systems), etc. For instance, this is FreeDOS.
https://www.freedos.org/download/
This is a wonderful (and long) list of general fallacies that people may hold about the operating system, as well as statements debunking them and proving why it is still a viable choice in 2025.
http://www.chebucto.ns.ca/~ak621/DOS/DOS-Fal.html
For us in the blind community, there are really only two issues standing in our way. The first is a good screen reader, and the second is software synthesis. Yet even these can be overcome. While many DOS screen readers were made in the past, only one is now completely open source. That is Provox. The entire code is available for us to update to our hearts' content. (Look down the page and you will find the download link under the screen reader section.)
Of course, we could create an entirely new one, but this gives us a good place to start if we don't want to reinvent the wheel. As for hardware synthesis, it was done in the past, with Flipper. It's not the best, but it shows that it is possible. Now, with all of these updates to DOS itself, as well as faster machines with better memory, soundcards, and drivers, it should be easier to create a software synthesizer.
There are still people programming for DOS, both for everyday use and versions of the operating system itself. Why not collaborate with them? Why can't we have a text-based, keyboard-driven operating system that works for us, that isn't bloated, and that we can even help to create? Imagine a version of DOS designed with accessibility in mind. What if it came with a built-in screen reader that talked during installation, braille support, a magnifier, ocr software, various other accessibility options, and menus that were easy to navigate for those who didn't wish to use the commandline, as well as access to it for those who did? What if it were free, or at the very least, extremely cheap, and could run on almost anything, so that anyone in the world could use it, provided he had some sort of computer? This is all within reach.
How many of you would be interested in at least trying out these modern versions of DOS to see what they offer and how far we could take them into the realm of accessibility and daily use?
#accessibility #blind #commandline #computing #DOS #FreeDOS #OperatingSystem #programming #ScreenReader #SoftwareSynthesizer #SpeechSynthesis #text-based #tui #WindowsAlternative
Wake up, new terminal type tester dropped
**ttypr** — A TUI for typing practice.
Supports ASCII, words and text mode.
Written in Rust & built with @ratatui_rs
Why AI is moving from chatbots to the browser https://thever.ge/VwGX #CommandLine #OpenAI #Tech #AI
I’ve been playing around with this and I can’t tell you how much I love this cli interface. It’s much easier for me, now, to edit and create new newsletters/emails. I’m super glad this newsletter platform offers this! it’s a lot cleaner, for me, than the web interface. As of right now, there’s a few bugs, but it still works well and i’ve already started contributing to the documentation! Providing some more notes for Windows users and explaining a few things that’s not in the original documentation. Buttondown CLI | Buttondown Documentation https://docs.buttondown.com/buttondown-cli #Cli #CommandLine @buttondownemail @buttondown #Terminal #OpenSource #TUI
Just published an article on my blog. If you're a RipGrep user, you should take a look. It might solve your issue.
https://andrewwoods.net/blog/2025/ripgreps-annoying-message/