• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: April 23rd, 2023

help-circle

  • My setup is not recommended, honestly. Old gaming PC from about 14 years ago with a couple extra hard drives, thrown in the closet with stripped-down Windows 10 on an old SSD, desktop version of Jellyfin, and an external drive for backups. Not even running in a Docker container because the CMOS battery is dead and getting to it is way too much of a hassle on that particular motherboard, so virtualization defaults to off whenever it completely loses power. Which it unfortunately does on occasion like winter storms, or summer heat, or if the wind is blowing.

    But hey, for the movies and shows we have on DVD/BD, as well as the music we’ve bought over the years, it does work for access from PCs and phones on the local network (Finamp + Jellyfin Media Player). I dabbled with IPTV for live TV replacement but found that only using totally free IPTV+metadata would take either much more work on no-virtualization Windows 10 than I’m willing to put up with, or have much more jank than my family is willing to put up with.







  • Onihikage@beehaw.orgtoLinux@lemmy.mlCrapped my system
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    Atomic means the core OS packages are in an immutable container such that none of its individual components can be updated separately; instead the entire container is replaced with a newer version when the system is updated. This makes it much less likely for something to break during normal use, and easier to rollback updates if something does happen to break. The ideal use case is a containerized environment where each app you use is installed in its own container, like Docker, or is otherwise self-contained such as flatpak installers, and doesn’t rely on any of the system’s packages.





  • When you’re keeping things in a tree structure for visual grouping and using containers to manage different logins, bookmarks will lose the tree structure, and you’ll have to specify which container to open it in. If your workflow involves a dozen tabs per context, locating the bookmarks and reopening them every time you switch contexts is a significant time and productivity loss.

    Consider the classic Evidence Board (also known as string wall, crazy wall, conspiracy board, etc.). Saving everything to bookmarks is the equivalent of putting your board’s contents into a drawer, then pinning everything back up whenever you need to look at or update that particular conspiracy. It works, but it’s cumbersome, error-prone, and wastes a lot of time; you’d only do this if you only have one board but multiple things to inspect. Leaving tabs open and simply unloading the inactive tab trees is like having multiple separate boards where you just roll them into a closet when you aren’t using them.




  • since most languages are written horizontally and i like ux to reflect this structure. such things are subjective though

    You might be misunderstanding what we mean by vertical tabs - we aren’t literally turning the tabs sideways and putting them on the side of the browser. We’re placing the tabs, still horizontal, into a stacked, scrollable list on the side of the browser. The superiority of this display method for tabs on widescreen displays is not subjective, and here’s why:

    1. Tab titles are not typically very long, but there tend to be a lot of them. This data is far more readable and accessible as a bulleted list than a long paragraph.
    2. Beyond about ten to fifteen tabs, tabs displayed at the top, side by side, must either shrink and obscure the title, go off-screen and be invisible without scrolling, or stack in multiple rows across the top. A vertical tab setup can easily display 30-40 of them in a vertical list, all with the maximum visible amount of their titles which helps distinguish them from one another.
    3. Modern desktop screens are wider than they are high, but webpage content scrolls vertically, often leaving a lot of empty space on the sides.
    4. Eyestrain is reduced and readability improves when the width of the reading area is reduced. This is why text on the web almost never fills the full width of a widescreen display, why most books are taller than they are wide, and why newsprint articles have many narrow columns rather than filling the entire page.
    5. Given points 3 and 4, tabs at the top of the browser window on a widescreen display leave slightly less room for the actual page contents, while tabs displayed in a vertical list on one side only cut into the white space that exists on the sides of the content, while keeping the titles readable and causing less eyestrain.
    6. With one change, a list can become an outline with sections and headers, following your own train of thought as you branch out and expand on each idea. In the same way, tabs displayed as a list can be very easily displayed with a tree structure, allowing tabs to be grouped, collapsed, and generally organized in ways that are impossible for traditional-style top-tabs.

    This is why Tree Style Tabs exists, though I prefer Sidebery these days, being more customizable and performant than TST. There’s no way I can ever go back to top-tabs.


  • I’d really recommend something like Fedora before trying to touch Arch. Arch is pretty much only one step removed from Gentoo, the difference being you don’t compile everything from source, but installing it is still a process of building the entire OS from the ground up. There is no GUI installer, you’re going to be in a terminal window punching in dozens of commands while the installation guide is up on your phone or a nearby computer. There is no real standard pathway to “a setup that works fine for most people”. The wiki is very noncommittal in many areas to the point of inflicting decision paralysis and wasting a lot of your time if you try to approach it as a Linux newbie, as well as throwing so many links at you that it can be hard to tell which links mean “you need to click this and follow the instructions” or “here’s background information on this thing we just told you to do that you only need to know if you’re curious”.

    When I tried to install Arch, following the directions as precisely as I could understand them, I couldn’t get networking to function when booted into the OS, it only worked when I was running the USB installation environment. The default pacstrap you’re given doesn’t include the same networking packages as the installation environment, so any newbie just trying to follow the guide is expected to chase down nests of links and hyper-detailed wiki pages to figure out which networking packages they need, try to get them installed, figure out how they’re supposed to be configured, and in my case, still fail to connect to the internet. Also not included by default are the packages that download manuals for all the commands you’ll be learning to use, or a text editor which you need to edit config files, and editing config files is the only way to configure most of the system when you’re in a terminal. I hit so many stumbling blocks and started over so many times it felt like a hazing. Gave up after a full day of trying to figure out the networking problem and having no new ideas the next day.

    Fedora (KDE Plasma/Wayland) worked really well out of the box with a proper GUI installer, I just had to do little configuration stuff like adding additional flatpak sources or learning how the console package manager works (dnf), and also to ignore any instruction that ever tells you to run dnf autoremove. Simple stuff like installing a web browser and basic apps was about as quick to set up as on Windows. The most trouble I actually had was with Discord - it would be freshly installed, briefly work, then on the next launch say that an update is available and demand I manually update it, with options to download an Ubuntu/Debian installer or a tar.gz (aka “figure it out yourself”) which never seemed to take. I ended up looking for alternatives that weren’t just using it in my regular web browser and discovering WebCord, which I’ve been very pleased with from a privacy perspective.