HNHacker News
TopNewBestAskShowJobs

thanato0s

654 karma · joined August 1, 2018

submissionscomments
thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I know it might sound surprising but I don't use that much Stack Overflow anymore :D I'm using the shell for many things, and the documentation is so good I don't need to go on Stack Overflow.

For problems I have in programming languages, either way I look at the implementation of some unknown stuff (class, function, and so on), or I go on the official doc.

Other than that, there are many solutions for browsing without the mouse (but they're not working for every website). You should look at qutebrowser, or some browser extension like Vimium or Pterodactyl. I speak about it quickly in the book.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
Thanks for your interest and your kind words!

I tried emacs (I like to try many stuff :D) but it felt a bit too much "program which does everything". I'm a big fan of small programs which can complete each other. You know, the Unix philosophy: "Make each program do one thing well".

I'm not a big fan of the keystrokes either, but maybe it's because I'm more used to Vim. Maybe I should try more seriously one day.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I'm happy you find the book interesting!

I speak quickly about mouseless ways of browsing in the book, and to me the best solution would be qutebrowser for browsing the Internet IMHO. You should check it out.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
Thanks for picking it! I hope you'll like it. If you have any question, feedback, or problem, don't hesitate to reach out. I'm always happy to help and I'll try to answer as fast as I can. My address email is on the page where I sell the book.
thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I thought about generalizing the information, but if I do that I'll have other problems:

1. The reader would bump into many more problems because the book is less focused. It's about installing a whole system, so many things can go wrong already, and I wanted to reduce the friction by being precise. To be precise, I needed to know what tools the reader would install.

2. I use these tools because I know they can teach a lot of fundamentals. This means that, when you're done with the book, you should hopefully have enough knowledge to swap anything you want, even the Linux distro.

I think you're on something about the sample. You can look at my blog though, there are many free articles (look at the "mouseless" tag) which are more general and capture maybe better the essence of the book.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
To me you're not a bad person :D thanks a lot for buying it! Maybe you should have looked a bit at the sample and the video before though, I don't want to deceive anybody.

There is no paperback copy available, because there are many commands and pieces of configuration in there, and I thought it would be easier for everybody to be able to copy and paste.

That said, if there is a demand, I would be happy to look at that.

Last thing: I explain everything in the book, so you don't have to stick with this system at the end, you should be able to build your own depending on your needs. You can swap any tool you want (even the Linux distro if you want), hopefully you should have enough knowledge to do that easily.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
It's intuitive because you're used to it. I thought the same, till I tried different ways.

I think it's just that: exploring new possibilities. I'm happy I tried mouse-driven and keyboard-driven workflow, because I could choose what I like the most.

I didn't know about Acme. Thanks for that!

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
Exactly. As I was saying in another comment, I have the impress that some people are very loud and dogmatic about these ideas: "you should NEVER use the mouse or I'll burn you as a witch on the village square!".

But I don't think the majority of the community around CLIs and keyboard-driven workflow are like that. It's just we like it, and we see benefits in this approach.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
That's something which is quite a paradox to me: many people will love using a GUI for coding, and at the same time they will use shortcuts 99% of the time. I don't get that.
thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I see a problem here: I'm not obsessing not using the mouse. There are some very loud people out there who are dogmatic anti-mouse. As a result, everybody speaking about a keyboard-oriented system is considered as a dogmatic.

It's not my case. I just think that when you deal a lot with text, like a developer, letting your hands on the keyboard is way nicer, instead of switching all the time between keyboard / mouse.

But I love to use the mouse when I'm on Gimp, or when I do some music, or when I post process some photos. You should use the best tool depending on the task.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
You should try to use qutebrowser. I quickly speak about mouseless ways to browse the internet in the book, I think qutebrowser is the best solution so far.
thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I'm using Arch for 6 years now, I never saw it crashing. It's the most stable system I've ever seen.

To me, "arch is unstable" is more an urban legend than anything else; the best is to try. And I can compare it to everything else I used for years: Win98 (oh my), winME (such a joke), win XP (way better), win 7 (really stable), Ubuntu (I had the impress to come back to win98 each time I was doing an upgrade), Debian (quite good), macOS (quite good because they don't allow you to do anything to crash the system, not nice when you have a problem). And so on.

And it's really not that difficult to install. I've one more chapter after the sample of the book I provide, and then it's done.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
Wow. That's a great and clear explanation. Thanks for that!
thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I totally agree with that. To me, flexibility is the way.

Something I hate for some GUIs: they sometimes change their interfaces without any reason. I think about the whole Confluence thingies (worst interfaces ever IMHO), or even intellij IDEs. When I was working with them, I saw the preference menu changing at least 4 or 5 times. Perfect to confuse me. That's why I accepted to try the tools my colleagues where using, the ones I still use today.

On top these tools allow us to have a configuration in plain text, which is so easy to manage because we have so many mature tools to deal with plain text (git is a great example of that).

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
It's not because you do jokes about a tool that this tool is not good.

> In any case, keyboard-only interfaces make the assumption that you know all of the shortcuts for each program you use

When I use Gimp, I need to know where are the different options I want to use. It took me time to learn where I can find the best tools for my own needs. It's the case for any interface, GUI or CLI.

But where some CLIs really shine: you can customize everything to create your own little world, to bring a consistency between all your tools. That's the real power: flexibility.

It has its drawbacks too, but I the benefits outweigh them big time.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I thought the same before trying to use my actual dev environment, but, at least for me, it felt more enjoyable to stop using the mouse when I was coding. I think the best is just to try both approach and see by yourself.
thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
The problem is not necessarily to be fast for me (I know people who are very fast with the combo mouse / keyboard) but more if you like it. If you don't enjoy working with your tools, you'll have a lot of friction to do your work.

I'm not sure everybody would like a development environment as I describe it, that's why I invite people to try Vim for example for a couple of week (I've some free articles on my blog about that) or i3, and see what they think about it. Exploring new possibilities is never bad.

About learning the tools: I agree, but you can learn much more from some tools than others. I think of Vim as easy to learn, hard to master because there is so many stuff you can do with it. But I used Intellij IDEs as well for a long time, and I don't think it's hard to master, because there's not so much you can master, except maybe the keyboard shortcuts.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I agree with most of what you're saying. Now, about the skills of the users, I think people are smart and can learn more easily than we think, if and only if they're taught right.

It's what I tried to do. I don't know if I succeeded, but so far I had only positive return, so it's encouraging :)

About the mix of both: I agree if I'm a long period on my keyboard or on my mouse, but not interleaving the use of both.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
These tools take a lifetime to master, that's true; but I could code in Neovim in two weeks. I think if you decide seriously to learn it, you can be effective with it pretty fast.

Easy to learn, hard to master. That's what I like, because you never stop learning.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I didn't think about that, but now you speak about it I think it's true. Thanks for that, that's interesting.
thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I don't hate the mouse, but I think staying on the keyboard when you work with text (like code) is way more comfy. The problem is not the mouse, it's always switching your hand between keyboard and mouse.

Additionally, the system I describe in the book is centered around the shell, and it has so many good and mature tools for you to deal efficiently with text.

I love the mouse for graphic design, music composition, photography (post processing).

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I would tend to agree with that, distros are not that different from one another in the grand scheme of things.

But there are still differences; I speak about them at the beginning of the book. For Arch Linux, the three important ones are for me:

1. Installing it teaches you quite a lot about Linux-based system. If you have any problem with another distro, you'll know pretty well what happens under the hood and you'll be able to debug the problem more easily.

2. Arch is a rolling release, which means that every program you use will be up to date. No need to wait for the next LTS like other distros. It has some drawbacks, but I think the benefits outweigh them.

3. It let you choose exactly what program you want. It doesn't install much by default. Freedom is important for me, and Arch just gives me that.

And did I speak about the crazy amazing Arch Wiki? And the repos which have... everything? Sorry I stop, I'm doing my fanboy here :D

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
Thanks! I hope you'll like it! If you have any question, feedback, or problem, don't hesitate to write me an email. It's on the page where I sell the book.
thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
Thanks for that. It's reassuring. I've always tried to do exactly that, and my readers were always thankful for this kind of direction, so... I continue :)
thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
Thanks!

I had a newsletter, and my subscribers were super helpful. Seriously, without them, I wouldn't have finish the book. I thought about keeping the newsletter, but I already had one for my blog. So I simply asked them to switch from one newsletter to the other.

I'm not sure it was a wise decision, but maintaining two newsletter, a blog, and a book was a bit too much for me. I'm still thinking launching a newsletter about mouseless tools though, with tips and tricks; maybe later.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I think that's true. It's always good to explore new ways, especially the ones you don't agree with. Even if you still disagree at the end, I'm sure you'll learn something.

I tried Ubuntu a couple of months ago, as well as other distros (elementaryOS, Linux Mint, and Manjaro). For Ubuntu, it's better than before. These distros had some interesting ideas, but I'm still very happy with my system :D

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
Change is part of life, isn't it? That was deep, I know :D

Seriously, maybe I'll write in 10 years "I was wrong: just install Ubuntu and you'll be happy". It will be a very short book though... but it's good to change and not staying in our little bubble.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I think it's good to be the devil's advocate. Different opinions are great to ask questions about our own.

I don't have any number, that's true. But I know that I enjoy using this system way more than any other I tried (including many "easy-to-use" Linux distros, Windows, or macOS).

As a result, when I discover this way of working, I began to participate way more in open source projects. In general, I didn't only like the result of what I was doing, I liked the way too. It changed everything for me.

I don't think we should always focus on the tools but more what we're creating with them. But if you use tools you truly enjoy using, I'm sure your productivity will increase as well.

This book is not to impose a system to anybody, it's more to dive into Linux and another way of working. That's why I explain everything in details: for anybody to shape their system and swap their tools as much as they want.

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
If I simplify a bit, I see two different approaches:

1. You write something broad as you say. You present many options to the reader. The book is not practical anymore, because you don't speak about something in particular but some general ideas. As a result, the readers can't really practice with a concrete project, and they might end up lost in an ocean of links. If I wanted to do that, I would have created another "Awesome list of Linux tools" on GitHub.

2. You write something more focused, as I did: the readers can practice, you can describe and explain everything they're doing because the focus is more narrow. You eliminate a whole class of problems as well, because you know exactly the tools they're installing and using. As a result, you enable them to understand what's happening.

I went for the second solution, because I think we lack books which are really practical. I wanted the readers to be actively engaged into a project, learn by practicing, and be able to swap every tool they want afterward. Because they'll have a deeper understanding of Linux, a modal editor, a tiling window manager, and so on.

It's not because I use these tools that I want to impose them to the world. I choose these tools for the book because they allow the reader to understand what's happening under the hood. Even if I was using another wm or another distro, I still would go with these tools, because it allows me to teach what I want to teach. Because they're not too difficult for beginners if you explain them right. I think people are smart, and I think they can learn way easier than most people think.

To me, Ubuntu is highly opinionated. Who cares? It's not about me, it's about what the readers can learn from the experience. I'm not convinced you learn a lot by installing Ubuntu, or that you understand the benefits to work with a tiling manager, or you understand the important place of the shell in the Linux ecosystem.

Thanks for the good luck :)

thanato0s··on Show HN: I wrote an entire book to build a mouseless dev environment
I used Pandoc for the PDF; the links don't work because it's a sample. They work in the real book.

About selling myself short: you're probably right. I'm struggling with imposter syndrome, like many, so I've a tendency to do that. At the same time, I'm trying to be honest and I don't want to deceive people.

← PreviousPage 3 of 4Next →