[YouTube] [Article] Cleanest Linux Productivity and Development Environment using Manjaro Linux

Hello all,

I've just published a guide for a clean Manjaro Linux based productivity and development machine. If you want to check it out:

Outline of the video and the article:

  • Why use Linux?
  • Why NOT to use Linux?
  • Comparison to Mac and Windows
  • Package Manager Comparison
    • Manjaro: Pamac
    • Mac: Homebrew
    • Windows: Chocolatey
  • Why Manjaro?
  • Hardware Setup
  • OS and App Installations
  • Use Case Example: Software Development
  • Use Case Example: General Productivity

All feedback is welcome.

thumb

6 Likes

If you want to contribute to this guide or want to change something, you can make a pull request on GitHub: https://github.com/soygul/QuanticDev/blob/master/articles/manjaro-linux-productivity-machine.md

Nice write-up.

As a seasoned developer I have accumulated some knowledge on how to have specific tools working the best way possible - that is without annoying issues like pacman file conflicts.

JetBrains tools
This can be done two ways - none of them involves a package manager.

  1. Download the archive and unpack it to designated tools folder in your home or another location where the user has read-write access (not counting sudo - so opt is out). Run the tool from the unpacked locations bin folder.
  2. Use Jetbrains toolbox (apps are installed to ~/.local/share/JetBrains).

Smartgit

  1. Install jdk-openjdk .
  2. Download the archive unpack to a local folder with read-write access
  3. Run the add-menuitem.sh from the bin folder.
  4. Then launch from the menu.

Node.js

Python development

  • Never use pip to install global python packages.
  • Use the package manager to install the package - usually python-pkgname .
  • If the package do not exist as a pacman package - use virtual environments.
  • My personal favorite is python-virtualenvwrapper https://virtualenvwrapper.readthedocs.io.

--https://github.com/soygul/QuanticDev/issues/2

1 Like

If you have any questions, you can check out Manjaro and Arch forums and wikis. They both have large and helpful communities. On the other hand, 99% of the time, you will not need to visit the forums since you can find answers to most issues on Google anyway.

The statements like the last sentence is why you got a :-1: from me.
When I use a genral purpose search engine I will mostly find links to the Arch forum or the Manjaro forum and then I neet to visit them. Sites like Superuser are also often among the top results and then I don't need to go to the Arch or Manjaro forums. But the advices there are too often not applicable.

I also see no real argumentation in your text. You just tell "from my experience", "in my opinion", "I recommend". What a critical would read from such a lack in argumentation: Manjaro is a distro for people who don't know what they are talking about.

and you will want to stick with specific versions of those tools during your projects.

A meniton that on a rolling release distribution like Arch you will generally find only the newest version of a package. But with programming languages, compilers and other development tools they keep several major versions of the toolchain like openjdk7, openjdk8, openjdk10, openjdk11 and openjdk in its latest version 13.

Arch Linux and derivatives, especially Manjaro Linux, have the best of the best package managers. You can find any package and their supported version in main package repositories, and user-submitted ones.

I know that mean here what I wrote about openjdk, but what you write is vague and almost incorrect regarding "any".

To sum up: This text is an endorsement from an application developer who has made good experiences with Manjaro, but isn't a specialist in Linux OS field.

3 Likes

Obviously, the entire narration is based on my experience. I tried to keep it as simple as possible, sparing the intricacies of pacman vs apt vs dnf sort of comparisons. However, I extend the articles over time, and people are already contributing to it.

and you will want to stick with specific versions of those tools during your projects.

This is based on my experience with versions of productivity tools. I didn't go into much detail for the sake of simplicity but took the liberty to say any since till now, I managed to find anything that I needed. i.e. Unity LTS (which cannot be found in Homebrew, Chocolatey, etc.): https://aur.archlinux.org/packages/?O=0&SeB=nd&K=unity+lts&outdated=&SB=n&SO=a&PP=50&do_Search=Go

But your summary is on point. The narrative is subjective. I would like to turn it into more evidence based paper over time though.

Also, below is a simple "how to enable AUR" search on Google. My usage is simple, so most answers that I get are on point.

Thanks for the input @linux-aarhus, I will fuse your feedback into the article over editing cycles. Saw the task on GitHub :+1:

Forum kindly sponsored by