• 3 Posts
  • 8 Comments
Joined 6 months ago
cake
Cake day: May 18th, 2024

help-circle



  • Logseq and Obsidian are only similar on the first look, but very different usage wise. Both are very open with a plugin system, and you can modify them to turn them into one eachother.

    So, if you want only FOSS, then Logseq is the only choices you have.

    But Obsidian is, even though it’s proprietary, very sane. Open plug-in system, active community, great devs who don’t have much against FOSS, and more.


    Obsidian

    • More similar to a classic note taking app, like OneNote, but with a lot of features. Hierarchical structure, and more of an “essay” style, where you store a lot of text in one page.
    • Page linking is only done when you think it makes sense
    • Has been a bit longer around than Logseq, feels more polished
    • Great sync and mobile app, which support plugins from what I’ve heard

    Logseq

    • Non-linear outliner. Every page is on the same level, but within a text passage, the indentation matters (parent-child-relationship)
    • You create a LOT of more pages. Most of my pages are empty. They are mainly there for linking topics. I rarely create pages manually.
    • The journal is where you write most stuff. You then link each block to a page.
    • Logseq a bit “special”. May not be for everyone. I for example am a bit of a disorganised thinker, who mentally links a lot of knowledge and throws concepts around all the time. Logseq is my second nature, because it’s more flexible. My GF on the other hand is more structured, and prefers something like Apple Notes, or, if she would care about note taking, something like Obsidian.
    • The mobile app isn’t great. It’s fine when I’m not at home, but the desktop version is the “proper” one, and mobile/ iPad a second class citizen.
    • Sync is only experimental for now. It will soon be officially supported (hopefully) and self hostable, but it worked fine for me.

  • I don’t see any problems with that. Even I (and probably most others here), who are FOSS advocates, think Obsidian’s model is fine.

    The devs surely get why FOSS is important, and try their best to match the pros of open source. They even stated that if the company goes bankrupt or they stop developing the app, they’ll open source it.

    One major thing they do absolutely right is how the notes get stored. On other note taking apps, it’s a proprietary database, often “in the cloud”, where your notes get hold hostage. Here, they’re just Markdown files, and the whole thing is pretty open, encouraging a strong community.

    It’s similar to Valve/ Steam. Proprietary, but liked by most Linux people.


  • Each to their own. Linux is, in my opinion, about choice. If one prefers everything to be ultra minimalist, native and lightweight, then that’s fine.

    I personally just find to be Linux’ most overlooked strength is containerization. It’s one of the main reasons why most servers run Linux, because of things like Docker. On the desktop, containers are way underutilized, but that’s now slowly changing with things like Flatpak or Distrobox.

    A distrobox container is technically more bloated than a native install, sure, that’s correct.

    But, in my opinion, it’s like saying “Drawers and closets are bloat for my apartment. I throw everything on the floor.” Yeah, now you have less things in your room, but it looks like shit, you can’t find anything and you fall over your tubberware that’s mixed with your underwear and shampoo.

    Having everything collected in a container only costs me a few hundred MBs and a small amount of RAM if needed. But, literally every PC has more than 50 GB hard drive space and 8 GB RAM. If your system slows down because of one container, then your PC is the problem, not distrobox.

    That absolutely doesn’t mean we should stop optimizing software of efficiency. But it can help us to spend our time on more important stuff, like fixing bugs or adding new cool features.

    I really love Flatpak because of that. Sure, it has some drawbacks, but as soon as more devs support Flatpak officially, and iron out some issues we currently have, like misconfigured permissions, they’re (imo) the best package format. Why should a distro maintainer have to apply every software change to their package format? That’s needlessly duplicated work.


  • Just a small (or maybe big?) tip for you 🙂

    If it’s for Linux, there’s a 50% chance there are no releases and 2 lines of commands showing how to build it (which doesn’t work on your distro), but don’t worry because your distro has it prepackaged 1 version out of date

    There’s a tool called Distrobox.
    You can install it (via CLI I think?), and then manage it the easiest graphically way via BoxBuddy (available in your Software Center), or just the terminal if you prefer it.

    With it, you can screw all those “Doesn’t work on my distro” moments.

    You’re on Linux Mint? No problems, here’s the AUR for you!

    ✨✨✨ BONUS: Your OS won’t break anymore randomly due to some AUR incompatibility, because everything is containerized! ✨✨✨

    Even if you run Arch, use it to install AUR stuff. Or Debian/ Ubuntu, add PPAs only via Distrobox.

    It’s absolutely no virtual machine. It basically only creates a small, lightweight container with all dependencies, but it runs on your host. Similar to Flatpaks.

    You can also export the software, and then it’s just like you would have installed it natively!
    Your distro choice doesn’t matter anymore. You now can run any software written only for Suse, an abandoned Debian version 10 years ago, Arch, Fedora, Void, whatever. It’s all the same.

    I hope that was helpful :)