• 2 Posts
  • 102 Comments
Joined 3 years ago
cake
Cake day: June 30th, 2023

help-circle
  • netvor@lemmy.worldtoLinux@lemmy.mlWhat WM or DE are you using now?
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    6 days ago

    i3

    With alacritty, qutebrowser, neovim and LibreWolf. I use my custom dmenu-based utilities for things like launching apps, locking (with slock), controlling (ie. postponing :D) redshift and music player and opening bookmarks, links and searches. Thunar is the most DE-like app I use but being comfortable with Bash i use Thunar just for certain tasks like organizing files like photos. For quick text edits, I sometimes prefer Mousepad. For screenshots it’s slop+maim.

    I don’t “rice”, I just set some color schemes years ago and use simple wallpaper (which I rarely see.) And keep everything as minimal and out of way as possible.

    (I don’t care about Wayland unless I’m somehow forced to. I mean, some of my utils depend on X11 for things like clipboard access but I suppose it could be fixed easily nowadays. However X11 works fine for me so if it ain’t broken…)


  • a moderator removing posts for a very far stretch interpretation of Rule 3

    …stretch by which party? in the sense that the post not really about self-hosting (and OP tried to use rule 3 in a stretched interpretation), or that the post was about self-hosting but moderator applied it in unnecessarily strict way? The way you phrased it seems like the former, but then why would that result in moderator resigning?

    (I’m not a native English speaker so sorry if it should have been clear.)








  • wanting to advertise for the little guy in general is kind of pointless, it feels good until you realize that in a healthy ecosystem there are just always going to be more little guys–the middle guys are selected from larger pool and the big ones are selected from larger pool of the middle guys … it’s the evolution. and evolution is all about niches and being good enough.

    the kind of link lists linked in the OP are actually awesome, but they are best served in larger number and in context. especially, if eg. i see someone make an insightful post or article and turns out the same person has a list of links, then it’s usually a treasure trove of more posts, articles, insights and even projects and communities. and yes, if i gave the link list to my mom it would be completely counter-productive, regardless of whether someone is a “little guy” or not. the littleness is not the point, the relevancy is.

    and sure you could make link lists that are assorted ranging topics with the main criterion “the author found it interesting and want to share it and/or come back later to it”, and while some of that cake is eaten by micro-blogging sites like mastodon or bluesky (esp. the sharing and quick discussion). outright simple, structured lists also have own kind of charm.





  • keeping all these containers up to date

    Updates are a good way to get the security holes fixed, but unfortunately it’s also often how the holes get in in the first place.

    I mean, for most projects it’s kind of sensible to assume that over long time, the code will become rather more secure and less buggy, so eventually the pros/cons might come out in favor of a strategy of updating every time. But it’s good to know that every update is inherently a double edged sword.

    That’s why I like the model that distros like Debian do: they keep the code stable for long time, and only send updates for which a typically independent party (package maintainer) has already decided that a given update indeed is a necessary bugfix, or even specifically a security fix. Similar policy of course could be applied to a Docker container as well, but I don’t know how many projects do this, and it would be a per-project policy, most probably not quite independent.




  • Don’t want to sound unappreciative, but the apps you refer to (and others in these threads) are not actually CLI’s but TUI’s.

    • CLI (command line interface) is when all interaction actually happens in the command line, ie. command + arguments. CLI’s are much simpler to implement, have little dependencies (pretty much just argument list, two data streams—stdout and stderr–and exit status) and typically one invocation means one independent task. All this makes CLI’s ideal as building building blocks of (semi-)automated workflows, but many CLI’s are also optimized for direct invocation from interactive shell, eg. by adding features such as output coloring, interactive yes/no steps or command completion (although that part is actually driven by the shell, and is quite independent from the execution of the app.)

    • TUI (text user interface, i think) on the other hand, is more like GUI but replicated within the confines of terminal emulator. The interaction heavily depends on terminal features such as moving cursor, resize notifications, etc. Also when TUI is ran, it’s normally used for zero to may tasks: e.g. I could start htop and investigate no process, 1 process or many, before quitting. Unlike CLI’s, TUI’s pretty much make no sense within automation.

    Don’t get me wrong: I love TUI’s (htop is one of my favorite and thanks for recommending nmon, i’ll have a look)–and often prefer them to GUI’s (eg. my text editor is nvim, which is a TUI app!), but in my post I was specifically interested in exploring CLI’s. I would actually love a similar post to mine but focusing explicitly on TUI’s as opposed to CLI’s.

    Sorry for long post – I hope it can kind of serve as explanation for people who are new to this and stumble upon this thread and aren’t quite familiar with the distinction.


  • Did not want to respond but this is hilarious.

    To be fair, really old CLI’s, like from the time when X.org was the new stuff, this style used to be more common. That was before “GNU style” (using single dash for single-letter bundle-able options and double dash for long options) became prevalent.

    But yeah, if you see -foo then you know the program is old enough that regular colonoscopy is recommended, and the original author is probably retired or “passed away at the ripe age of …”.