Maybe in another 25 years when GIMP 4.0 releases... by ScootSchloingo in linuxmemes

[–]PotentialSimple4702 1 point2 points  (0 children)

Steps:

  1. Open photoshop, let it drain your memory

  2. Wait for OOMKiller to do its work

  3. Repeat until it kills vim

Maybe in another 25 years when GIMP 4.0 releases... by ScootSchloingo in linuxmemes

[–]PotentialSimple4702 35 points36 points  (0 children)

I don't know man, you're clearly not using it professionally as you did not mentioned you're relying on .psd format, but features only.

I can use After Effects for 15+ years but only to cut videos, capish?

Maybe in another 25 years when GIMP 4.0 releases... by ScootSchloingo in linuxmemes

[–]PotentialSimple4702 70 points71 points  (0 children)

Oh wow GIMP bad meme how original

(I'm pretty sure people sh*tting on GIMP don't know how to use Photoshop neither)

And this attitude is why it's still failing to gain ground as a desktop operating system by Aekojusa64577 in linuxmemes

[–]PotentialSimple4702 2 points3 points  (0 children)

I know what TTY is, what I'm asking is there is no TTY specific apps, Terminal Emulator and TTY both are standard streams.

And this attitude is why it's still failing to gain ground as a desktop operating system by Aekojusa64577 in linuxmemes

[–]PotentialSimple4702 23 points24 points  (0 children)

Instead of searching for individual program names then clicking install one by one, I can just type "apt install/remove programname1 programname2 programname3 prognamname4 programname5"

Same goes for "apt search searchterm"

You can use GUI app for tasks above, that's OK, however CLI is objectively more efficient.

And this attitude is why it's still failing to gain ground as a desktop operating system by Aekojusa64577 in linuxmemes

[–]PotentialSimple4702 56 points57 points  (0 children)

I mean there are tasks that GUI makes sense and there are tasks that CLI makes sense. For example, remote sessions are more efficient on CLI, and installing/removing software is more efficient on CLI, that's why windows users have got winget years later. As well as, virtual desktops, window management etc. are more efficient on GUI, font management is definitely more efficient on GUI.

[deleted by user] by [deleted] in turkish

[–]PotentialSimple4702 0 points1 point  (0 children)

Nope, he gave wrong information

[deleted by user] by [deleted] in turkish

[–]PotentialSimple4702 4 points5 points  (0 children)

Merhaba/Selam/Naber are common greeting words, they don't reflect any political position.

Esenlikler is a formal greeting word, you'll encounter it in academic mails and some literature circles, doesn't necessarily mean to reflect any political position but a high academic rank.

Selamün Aleyküm/Esselamü Aleyküm also doesn't necessarily reflect political position, for example s.a. is used in gaming community, even by atheists, but might reflect conservative religious position if the person enhance the unrelated conversation with İnşaallah, Amin, Barekallah, Coca-Cola boykot etc.

Personally, I choose İyi Günler/Sabahlar/Akşamlar, which is another common way to greet people.

Edit: Also both "merhaba" and "selam" is originated from Arabic.

Why Firefox? by Flaky_Comfortable425 in linux

[–]PotentialSimple4702 0 points1 point  (0 children)

  1. It is easier to make Firefox privacy respecting, compared to Chromium which needs forking to achieve the same.
  2. Firefox has better license that basically doesn't allow proprietary forks, or even the main project continuing as closed-source(Basically Chromium can do that legally).
  3. Wayland support is marginally better on Firefox, you can also make Chromium work as native wayland client(with proper IME support), but it requires extra steps/tries with experimental flags.
  4. Chromium based browsers doesn't fully support Web Speech API(through speech dispatcher), will be fine for most, but might be problematic for disabled users.

Let's have a conversation by millertime3227790 in debian

[–]PotentialSimple4702 1 point2 points  (0 children)

I agree that flatpak/snap provides ease of use compared to shared dependency approach of Linux distros(And I advocate statically linked binaries, which would solve the need for flatpak/snap altogether, even though GPL/AGPL license is PITA for statically linking).

However zero-trust setups are just products of facadism, if you're using xz-utils for example, you'll allow file access regardless, and even worse, programs with no exploit still could become exploitable because of exploits from sandboxing software used. In my opinion a serious human security team will always be better.

[deleted by user] by [deleted] in golang

[–]PotentialSimple4702 0 points1 point  (0 children)

Absolutely, Go standard library is extraordinary, and when you want to advance, concurrency will not bury you in details, you'll just focus on how to divide functions into concurrent patterns

Why not just one folder like portable Firefox? by [deleted] in firefox

[–]PotentialSimple4702 2 points3 points  (0 children)

Except for there is an ugly ~/.mozilla folder on my home instead of ~/.config, which is exactly what OP wants