• 0 Posts
  • 24 Comments
Joined 7 months ago
cake
Cake day: June 30th, 2025

help-circle
  • I still don’t see how this is an argument for “I do not want to learn.”

    Because this is just one thing that you clearly know how to do and probably enjoy.

    I don’t know how many of the following things you are good at and enjoy, but the same argument applies to all of them: cooking, knitting, repairing a car, welding, growing crops. All of these are desirable and apply to things that most of us use regularly. But you just cannot expect everyone to learn them all in order to enjoy the products they could create or enhance by them. It is not problematic to say you just want to use something and not learn everything that is necessary to create or master it.

    If you cannot see that this is true of a CLI, then I have run out of ways to try to explain it to you.


  • Just for the record, these are not the same questions you asked in your first post. But to answer them: nothing is different about this. But at some people don’t want to keep learning how to use stuff, they want to start using it. And there’s a difference between “learn how to use a new vacuum cleaner” (to give a particularly obvious example) and “learn how to use a completely new paradigm that is different from everything you have used before and doesn’t have a clear starting point”. (And before you say that the first steps are easy, let me rename all commands in your CLI and see how quickly you find out how to read a man page.)

    Mind you, I’m not talking about myself, having used CLIs since the 80s, but just because I know how to do something doesn’t mean it should be a fun activity for everyone.


  • It’s not, though. Tying a command doesn’t take a lot of time, but learning what commands are useful in a specific situation does. Even “ls -la” is an achievement you need experience for. And it doesn’t help that if you get stuck and ask (around here or in other enlightened circles) the answer you receive is usually some variant of “Have you read the 40-screen man page?”







  • Ok, thanks for clarifying. I was asking for a statement in support of your initial claim that turned out to be completely wrong: they didn’t duplicate the code upon creation of the project, they didn’t create a fork under their control, and they don’t make independent changes to the code.

    What they are doing is customising the current code of Firefox at the time of compiling the LibreWolf project. If you really insist that that is a fork, then one of us doesn’t understand what a fork is, and I’m not going to continue a fruitless argument.


  • Interesting, because there is no mention of that anywhere on their website. Indeed, the workflow overview in their source repo clearly states that in order to build LibreWolf, you need the current Firefox source tree, and this is reflected in the Makefile, which fetches the Firefox source tarball associated with the same version. Nothing points to a repository they created at any prior point.

    Can you link to some official statement that supports this claim?