• 22 Posts
  • 2.03K Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle

  • Most developers I’ve looked at would happily just paste the curl|bash thing into the terminal.

    I mean, I typically see it used for installing applications, and so long as TLS is used for the download, I’m still not aware of a good reason why you should check the Bash script in particular in that case, since the application itself could just as well be malware.

    Of course, it’s better to check the Bash script than to not check it, but at that point we should also advise to download the source code for the application, review it and then compile it yourself.
    At some point, you just have to bite the bullet and I have not yet seen a good argument why the Bash script deserves special treatment here…

    Having said that, for cases where you’re not installing an application, yeah, reviewing the script allows you to use it, without having to trust the source to the same degree as you do for installing an application.


  • One thing that will become important pretty quick if you continue making these scripts is that it’s almost always better to wrap your variables in quotes - so it becomes yt-dlp -x “$a.

    Oh man, this reminds me of the joke that any program that’s more complex than Hello World has bugs – and folks still don’t even agree how to spell “Hello, World!”.

    Of course, Bash is a particular minefield in this regard…








  • It’s just really oversimplifying memory usage. OS designers had that same thought decades ago already, so they introduced disk caching. If data gets loaded from disk, then it won’t be erased from memory as soon as it isn’t needed anymore. It’s only erased, if something else requests memory and this happens to be the piece of “free” memory that the kernel thinks is the most expendable.

    For example, this is what the situation on my system looks like:

    free -h
                   total        used        free      shared  buff/cache   available
    Mem:            25Gi       9,8Gi       6,0Gi       586Mi       9,3Gi        15Gi
    

    Out of my 32 GiB physical RAM, 25 GiB happens to be usable by my applications, of which:

    • 9.8 GiB is actually reserved (used),
    • 9.2 GiB is currently in use for disk caching and buffers (buff/cache), and
    • only 6.1 GiB is actually unused (free).

    If you run cat /proc/meminfo, you can get an even more fine-grained listing.

    I’m sure, I could get the number for actually unused memory even lower, if I had started more applications since booting my laptop. Or as the Wikipedia article I linked above puts it:

    Usually, all physical memory not directly allocated to applications is used by the operating system for the page[/disk] cache.

    So, if you launch a memory-heavy application, it will generally cause memory used for disk caching to be cleared, which will slow the rest of your system down somewhat.

    Having said all that, I am on KDE myself. I do not believe, it’s worth optimizing for the speed of the system, if you’re sacrificing features that would speed up your usage of it. Hell, it ultimately comes down to how happy you are with your computer, so if it makes you happy, then even gaudy eye-candy can be the right investment.
    I just do not like these “unused RAM is wasted RAM” calls, because it is absolutely possible to implement few features while using lots of memory, and that does slow your system down unnecessarily.




  • Yet more suggestions which you didn’t ask for:

    1. GitNote might be up your alley. Its UI is not as slick as QuillPad, nor does it have as many features, but it does faithfully keep the folder structure.
      Somewhat of a deal-breaker for me personally: It can’t do reminders.

    2. Embrace the chaos. 😅 I have a little program for managing my notes on desktop and it just dumps them all in one folder, too. If I need to find something again, I’ve got a little text search, which is basically the equivalent of grep -iR. I just make sure to mention enough keywords in each note, so that I can find it again.
      Personally, I much prefer this workflow, because you can start typing (and hitting Ctrl+S) and then later ensure that it has all the right metadata, rather than having to select a folder upfront where it will be saved.

    I actually tried QuillPad not too long ago and couldn’t make it work for me, but being able to save as normal files seems to be a recent addition, so maybe that’s what I was missing.
    I’ll probably try setting it up to work with my desktop note system then…





  • To be honest, what I’m most mad about isn’t the typoes, it’s that someone generated this image and figured, yeah alright, that will clear things up.

    On some level you want to believe that even if someone does not come up with a proper concept for a visualization, that they still check what the AI shat out, so that it’s at the very least not conceptually wrong and not confusing.

    This image isn’t just shitty, it’s actively worse than having no visualization. They could’ve generated that, chuckled, and not used it. Just how do you blunder your perception check so badly that you decide to include it anyways?




  • Ephera@lemmy.mltoLinux@lemmy.mlKDE Plasma 6.6 released
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 days ago

    Yeah, I’ve done that occasionally, too, but it adds a load of friction for moving windows between screens, in particular also when un-/replugging the screen, so it’s still painful enough that I don’t bother with a second screen.

    I guess, it also plays a role that I do use lots of workspaces, so it’s 1) extra painful and 2) I don’t have as big of a need for a second screen, since I can just switch out what first screen displays very quickly.