• 0 Posts
  • 129 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle



  • Ok, I’ll try again:

    Again a solved problem, just make a decent GUI for your application.

    You are promoting monolithic design. You completely fail to comprehend Unix philosophy:

    1. Expect the output of every program to become the input to another, as yet unknown, program. Don’t clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don’t insist on interactive input.

    GUIs are only used for human/application interaction. They are not needed for application/application interaction. While it is not unreasonable to have a GUI for interactive input within your application, it is infeasible and undesirable for a GUI to be needed for your application to interoperate with other applications.

    Go ahead and create the GUI if you really want, but expect your users to want to call it from a shell script. Give users the capability to automate away unnecessary manual interaction, and allow the machine to take up that pointless busywork.

    So googling how to do someone, copy/pasting command is better than finding it in GUI?

    Oh, absolutely. Especially for a one-off setting that you might never look for again. There’s just no sense in wasting the time building up a complex GUI to handle every possible interaction a user could ever want to employ.

    The solution to the “problem” of “needing to use the terminal” is to retrain the user to understand how limiting even the best GUI can be, and to greatly prefer the terminal.

    So, my suggestion is, rather than try to hide away the terminal, it should be featured prominently, exposing the limitations and shortage of command line applications available to windows users. An effective, powerful, well-supported terminal is one of the major benefits of Linux.


  • Are you suggesting users with no programming experience can simply add the flags they need to a terminal application but would be unable to do the same with a GUI because the GUI is the barrier?

    Yeah, why not? I’ll go ahead and make that suggestion.

    I mean, the terminal allows them to ctrl-c, ctrl-v a simple solution developed by someone else, even if that someone else didn’t bother to build out a GUI for applying their changes.

    The convoluted steps they would have to take to achieve the same effect with a GUI would seriously hinder the GUI-only user.

    What I am really saying, though, is that the problem of “needing to use the terminal” is not actually solved by ensuring that every possible setting can be accessed and manipulated with a mouse.

    I’m saying that the best way to solve this “problem” is by pushing the user to expect and even demand the terminal. Distros should autolaunch a terminal window at startup. Put it right out there, front and center. Invite the novice user to interact with it with friendly little toys like fortune, cowsay, sl, toilet, espeak. The insane usefulness of the various shell tools are more than enough to keep them using it.







  • It’ll take you public IP and translate those packets to use your internal one.

    That is NAT, yes. But that is only one small function that a router can perform, and not all routers have NAT enabled. You only need NAT if your ISP only allows you to use a single IP address.

    If your computer has an address that starts with 169, 168, or 10 there is a NAT somewhere in your network.

    That’s not actually true. I can create such a network without connecting it to the internet, no NAT. I can create a second network, again, no NAT. I can then use a gateway router that allows any node on the first network to reach any node on the second. That router is still not doing any NAT. It’s just passing traffic between two networks.


  • “Pressure” is typical. “Discomfort” is typical. If you don’t have an underlying condition like a sinus infection, “pain” is not typical. You might want to talk to an ENT.

    I’m a balloon pilot. My ears will typically first equalize about 500 feet above ground level. I’ll occasionally hear small little “farts” as the pressure changes, but I rarely feel anything more than slight pressure.

    but multiple times I’ve gone from sea level to between 5k and 10k feet, and when my ear pressure equalize, it is often quite painful for minutes.

    If your ears aren’t equalizing until a 5k ascent, that’s approximately 2psi pressure differential. I can see how that would be quite painful.

    If your ears won’t clear at all, yes, you’d have a problem. But, you’re indicating your ears do eventually equalize. You won’t experience more pain than what you already do.

    Even though there is an 8psi difference between cabin and atmospheric pressure, your sinuses apparently start “leaking” at a 2psi differential; they won’t build up an 8psi difference across your eardrums.

    You might try a nasal/sinus decongestant before an ascent. Pseudoephedrine works best for me, but it tends to make my head swim. Oxymetazoline nasal spray works well, but I get terrible rebound congestion from it. Phenylephrine pills do nothing, but phenylephrine nasal spray (“4-Way”) works very well for me.