Live data from Hacker News

Show HN: Frogmouth – A Markdown browser for the terminal

github.com

11–20 of 71 posts

Re: Show HN: Frogmouth – A Markdown browser for the terminal

#11

I'm a big fan of the Markdown Preview feature in VS Code Honest question: why do developers insist so much on using command line based tools? What's the advantage over using an IDE? (e.g. VS Code or PyCharm)

For me, it's focus.

Re: Show HN: Frogmouth – A Markdown browser for the terminal

#13

I'm a big fan of the Markdown Preview feature in VS Code Honest question: why do developers insist so much on using command line based tools? What's the advantage over using an IDE? (e.g. VS Code or PyCharm)

- most programmers in general are really fast with keyboard , like maybe 80-90 avg most of them so using the keyboard most is a good way for speed & consistency - another example i can give is maybe you have some error on your ide that you can't debug for some reasons, most probably you can't copy text from that window, (it's just an example maybe you'll similar issue in other ways) having cli means you can copy whatever the program is throwing at your, theres not limit - another thing is aesthetic: you know you can do a lot.of stuff from cli, all will have the same color scheme & consistency across every cli programmes which someone may prefer. - lightweight

Re: Show HN: Frogmouth – A Markdown browser for the terminal

#14

I'm a big fan of the Markdown Preview feature in VS Code Honest question: why do developers insist so much on using command line based tools? What's the advantage over using an IDE? (e.g. VS Code or PyCharm)

IDEs are often big, slow, costly, inconsistently featureful, subject to the vagaries of personal taste and fluctuating support, difficult or impossible to automate, and not always available (either not installed, not possible to install, or just expecting a graphical interface that is not local to the operator)

TUIs/CLI programs are (generally) small, composable, consistent, reliable, fast, well-supported, installed by default or easily obtained, predictable, have good keyboard shortcuts, and they work great remotely.

Re: Show HN: Frogmouth – A Markdown browser for the terminal

#15
post #5

Earlier quoted context omitted.

Speed, consistency, customization.

I get all three of those w/ my VS Code setup...could you explain in more detail?

Your hands almost never have to leave the keyboard.

There is often not telemetry.

You can remotely connect from a different machine and you your development environment.

The cross-platform story is much better. For example, supporting BSDs.

It exposes you to a lot of details hidden or abstracted away by GUI applications.

Also, its a matter of preference.

Re: Show HN: Frogmouth – A Markdown browser for the terminal

#19

I'm a big fan of the Markdown Preview feature in VS Code Honest question: why do developers insist so much on using command line based tools? What's the advantage over using an IDE? (e.g. VS Code or PyCharm)

I used to prefer Vim but moved to using IDEs. In professional development, you want to use the best tools - a forklift vs. a shovel. I don’t think text editors are the best tool for that, but why do programmers insist on using worse tools?

From my previous experience, I’d guess it’s these psychological factors:

1. IDEs have more cognitive overhead, and programmers have to keep a lot of state in their heads. So using a text editor gets out of their way initially to get started developing. In the long-run, though, it’s worse for cognitive overhead because you have to keep more state in your head due to having worse code completion. You also have the additional effort needed to set up plugins with text-based tools to provide additional features that are helpful for daily tasks.

2. IDEs tend to have more knobs - big menus, dropdowns etc. Those can reduce your ability to focus when you’re not used to them. Many of the available options likely aren’t applicable to what you’re working on, and can be distracting.

3. A lot of programmers have a sense of elitism, and using text-based tools looks retro and more intimidating to those not familiar with it. In so doing, this validates the view of oneself as a member of a priestly class of text-slinging wizards.

4. Programmers love to yak-shave. Using more primitive tools gives a reason for us to customize the experience, even or especially if it’s an inefficient waste of time. Programmers love opportunities for self-expression through code and customizing the experience of using their coding environments for its own sake.

Re: Show HN: Frogmouth – A Markdown browser for the terminal

#20

I'm a big fan of the Markdown Preview feature in VS Code Honest question: why do developers insist so much on using command line based tools? What's the advantage over using an IDE? (e.g. VS Code or PyCharm)

You get an endlessly customizable setup with a single interface. Build, write, read docs, test, lint, debug, troubleshoot, admin. Same interface. All keyboard driven, so I don't have to switch between keys and mouse.

It's extremely portable, works exactly the same on my machine as it does on any OS with bash and vim, it's easy to use on a remote machine.

It's easily scriptable as well which makes customization simple. It's way faster for me to write a quick script to do something I need then dig through an endless list of marginally verified plugins to do something.

I guess my question is what can you do with an IDE that can't be done at the CLI?

I've tried code, pycharm, eclipse and really never found a value add.

And all of that applies to other tasks beyond coding. Notes, email, chat, it's right there, hey what's the price of that stock my buddy was talking about? Yep, right there. Hey look also my music.

Post reply on HN