283: The State of IDEs: VSCode or BS-Code?

This week’s episode of Destination Linux, we’re going to be talking about IDE monopolization is it going to be an issue in the future? Then we will be discussing Thunderbird going mobile. Plus, we have our tips/tricks and software picks. All this and more coming up right now on Destination Linux to keep those penguins marching!

Sponsored by: do.co/tux2022
Sponsored by: bitwarden.com/tux

Hosts of Destination Linux:

Ryan (DasGeek) = dasgeekcommunity.com
Michael Tunnell = tuxdigital.com
Jill Bryant = jilllinuxgirl.com

Want to Support the Show?

Become a Patron = https://tuxdigital.com/contribute
Store = http://tuxdigital.com/store

Community Feedback

You can comment on the forum thread below or fill out the contact form at https://tuxdigital.com/contribute


Leave a Comment

Notable Replies

  1. Like Jill said: “It’s a good thing we have … emacs … heeheehee …”. :grin:

  2. After listening to the episode I was wondering, is there a difference between an IDE and a text editor? My understanding of an IDE, is an application where you can edit and run the code from within that application Wikipedia definition.

    Am I misunderstanding the intent of the podcast?

  3. Cloning ChrisAtTheMachine’s build is a completely different animal to actually using it as awesome as it is.

    I think the big difference is copying vscodium’s features in *vim means stepping well outside of official support and while you’re supposed to do that, you’re still having to develop features yourself and/or inherit all the quirks of a ton of personal projects which’ll usually (though not always) have a sole maintainer who may or may not be active, may or may not care 1/2 a whit about repo security, have zero if not near-zero documentation spread out all over the place and have a limited pool of people who can help you if you get stuck with that particular part of your build.

    I now use micro (no plugins) and a ton of bash though that’s after ~2 years of beating my way into near-exclusive use of vim (which was near identical to neovim for my purposes) until I just got fed up of constantly having to futz with it and educating my way into obscurity. If someone takes to it and values freedom i’d say *vim all the way and I think everyone should learn basic vi but in my opinion it’s not the simple alternative it’s often billed as and it’s asking for a heap of work you wouldn’t otherwise have.

  4. I love vim and I use it, I never had the need to use anything else, but my use case is and always was pretty basic. Though I would rather recommend to learn vim or even neovim (never tried that one) and adapt or incorporate it into your personal workflow instead of just copying the dot files from the web by somebody else.

Continue the discussion at forum.tuxdigital.com

5 more replies


Avatar for vinylninja Avatar for Ulfnic Avatar for Fabulous_Phil Avatar for MichaelTunnell Avatar for umop3plsdn Avatar for oaguy1 Avatar for PatPlusLinux Avatar for Adda Avatar for ak2020