Am I missing something here? If minimalism is the goal, why stick with a horizontal panel? Is there a way that folks typically configure this to make it more useful (or less obtrusive)?
1,229 karma · joined May 1, 2018
Am I missing something here? If minimalism is the goal, why stick with a horizontal panel? Is there a way that folks typically configure this to make it more useful (or less obtrusive)?
This has been my general strategy for personal data. I have also been trying to figure out if there was a reasonable way to get long-term very-cold storage (e.g. backups of family pictures). Something that would last decades just sitting in a fire-box somewhere (reasonable temps, no moisture). Been considering https://en.wikipedia.org/wiki/M-DISC, but interested to know if anyone has other ideas...
If you do not want to host your own instance, there are many great providers who will host one for you at a low cost.
That being said, one of the main benefits I am hoping to get out of Silverblue on the desktop is relief from the almost-inevitable system degradation I have experienced with other Linux distros where, over time (and especially with major upgrades), more and more things slow down and/or stop working. I am not sure if I am just doing something wrong (besides daily heavy use), but historically all my desktop Linux installations have become almost unusable after a couple years. I am only a few months into using Silverblue, but I am hoping that the way the system image is rebuilt for each update makes it more stable in the long-term....
If you are the kind of Linux user that treats your OS like a pet, with lots of TLC and endless tweaking to get things "just right", then Silverblue is a terrible choice. It is way more difficult and time-consuming to "hack" stuff together at the system level.
However, if you prefer to treat your core OS as livestock (something rigidly structured and reproducible automatically), then I highly recommend giving Silverblue a try!
As a software developer, I run a lot of random software/dependencies/etc and I have historically struggled with my Linux system stability degrading over time as I add/remove packages and config. My goal with Silverblue is to have a solid base OS that does not suffer from package-drift over time. On top of Silverblue, I use distrobox to run many of my apps/bins in a virtual container. That container is where I do all my "hacking" to get things to work and I consider the container to be expendable. If I start having issues with it working correctly, I can just blow away that container and rebuild it without effective my core system, other containers, or the flatpak apps.
That being said, if I had to choose, I think I would prefer to increase my income instead of decreasing the cost of items I had to purchase. (Of course, both would be best!) Lower cost items only benefit me, if I need to purchase them. With an increased income comes an increased set of options for how to deploy that income.
I found the discussion in the Deseret piece regarding how the result of the Alaska senatorial election seemed "unintuitive" to many voters to be very interesting! When I look at the numbers and results in that election is seems clear that the outcome is exactly what I would hope to see (and seemingly is a text-book case of RCV in action). But alas, when you deploy to production, things rarely go as planned and it is clear that I need to give more weight to the human element in all of this. Even if the results are statistically desirable, that does not mean that voters will actually feel good about the result of the election....
I am very interested in the amount of negative sentiment to RCV in the zeitgeist and am trying to determine if it is coming from lived experience of issues with the voting system or from somewhere else....
Good enough that IMHO the benefits clearly outweigh the concerns. The beauty of the fragmentation of voting in the US, is that we can roll out different voting systems incrementally and be able to collect data on how they work without "betting the farm" on one election.
Until it becomes the a "both people are lunatics" sort of decision....
> Third parties aren't going to be a real thing in the US without a change to the way we count votes.
Exactly. Perhaps the single most important (feasible) improvement that could be made in US politics is broader adoption of Instant-Runoff Voting! It keeps things simple, maintains single-representation, but avoids the absurdity of first-past-the-post voting.
I think your point here is that typically with software, changing one line of code means that you need to rebuild the entire executable.
Your analogy breaks down pretty fast, though. While fixing one thing on a car _never_ requires totally rebuilding the thing from scratch, there are still tons of interlocking dependencies and architectural challenges that can impact the time/complexity required to change out a part. (See the effort required in most vehicles to change simple wear items such as a timing chain or a water pump....)
In my experience of software, most of the "rebuild pain" is self-inflicted by the project maintainers (poor automation/containerization of the build process). Software has the luxury of abstraction and automation that can reduce the build effort required from an individual in ways that a mechanic could only dream of!
As a side note, for years I used a Nexus 6. Great phone (the battery was getting sketchy, but the rest of the hardware held up well for 7 years of use)! With LineageOS, I was getting a steady stream of software updates. I was finally forced off of the phone when they killed the 3G networks here in the USA (and apparently the Nexus 6 did not support VoLTE....).
We are all intentional about _over communicating_ what we are working on and where we will need support from from each other. Everything else pretty much just flows naturally from that. There are (rare) times were I cannot progress on something that day because I need feedback from someone who will not be online for 10 more hours, but it is just a built-in assumption that this will happen and I always have other work queued up that I can do if I get stuck....
https://antennapod.org/ is incredible! 10/10, highly recommend!
If I need a proprietary app to access a show's feed, then IMHO it should not be considered a podcast (and I refuse to listen to it).
That being said, I remain cautiously optimistic about the podcasting ecosystem. A huge number of high-quality shows remain freely available (and many shows sustain an independent revenue stream). Despite the creeping centralization, podcasting still feels very independent when compared to things like Youtube/Tiktok.
My takeaway is that proper data modeling at the initial stages of designing a software architecture is absolutely essential to long-term scalability. You really need to consider the type of data you are storing, its shape, and the access patterns involved with reading/writing it. Of course, since it is basically impossible to get this correct the first time, it is even more important to have a good abstraction layer between your business logic and your database to make it possible to change your data store in the future.
- Maintain documented requirements for ALL CODE FUNCTIONALITY - Maintain tests for ALL REQUIREMENTS - Be able to produce reports for auditors that prove linkage between the requirements and the tests (to prove that all requirements were tested)
In this context, Cucumber was really nice since it automatically solved all three of these at once! For general testing purposes, though, I think Cucumber has too much overhead for it to be worth using...
Probably the most important thing was that with a lot of test frameworks, having poorly architected test utility code is annoying and more time-consuming, but has a limited blast radius. Hacky tests can be easily isolated from the other test code. In Cucumber, proper architecture and reusability are paramount. If you screw this up, your tests become unmaintainable really quickly!