A human who has opinions

  • 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle



  • I’m a guy who prefers community based distros. They don’t have business decisions get in the way of the needs of the community. It ain’t perfect, but it’s worth the tradeoffs for me. Debian for stuff I don’t want to constantly mess with. Arch for the express purpose of constantly messing with (and sometimes messing up).




  • Helping a strategic trade ally and making it clear that they have the backing of the US in more than just words seems to me like something that would make invading Taiwan even more risky than an amphibious invasion would already be. It’s not like Taiwan (or the US) is going to invade the mainland, so I can see why this is, and has been, the foreign policy of the US. The US aircraft carrier group that’s patroling the area and the commitment to defend Taiwan in the TRA are already a thing. This is just following through on commitments already announced. I don’t see a way that this transfer of weapons could be used as a pretense for an attack where the international response wouldn’t be extremely negative towards mainline China. I don’t agree with a lot of the foreign policy of the US, but I can see how they justify it with their own interests.







  • For general gaming news, I go with Jeff Gerstmann and the Nextlander guys. For more technically focused stuff, it’s hard to beat Digital Foundry and their methodology of focusing on the user experience over benchmark numbers. I think all of those folks have been around long enough to be above chasing the hype cycle for traffic and they all have context from decades of being in the industry. Rich from DF started working in games media in 1990 and Jeff started working at Gamespot in 1996. It’s hard to find other folks who have been in the industry that long and still working in games coverage.





  • While Arch does allow a user to do a lot, including breaking their system, I would note that it’s not a herculean task to build and run a stable machine. I broke my Arch system a few times by going against best-practices and it did teach me about some risks, but I knew exactly what I did and why it broke every time. It taught me how to quickly recover, which is good to know for any OS.

    I’d call myself an intermediate enthusiast and I don’t have a career that uses Linux, but I have never found Arch “hard”. It just takes some reading and a little patience. The Arch Wiki has a majority of the answers, but if you have tried and failed to find the answer you need, the community is extremely savvy and are there to help you. They just prefer you to dig into the wiki and try for yourself before asking for help.


  • For desktop Linux, I use Arch. It’s a community driven base distribution, so the needs of the community are what drives development and there are no financial decisions of a company that get priority, which is refreshing. It also has access to the latest and greatest that Linux has to offer.

    They have a philosophy of expecting basic effort from users and to have a tinkering mindset. Historically, Arch devs and users have a reputation of being grumpy greybeards, but many of the rough edges have been rounded off in the last few years. If you are willing to do a bit of reading or watching some YouTube videos, it’s not really that hard.

    You can really build a lean and powerful machine that has just the software you want on the system with Arch. All it takes is a little effort and willingness to ask for help from the community after you have tried and failed to solve problems yourself. It’s really not the badge of elitism to use Arch in 2023. It’s never been easier to use and doesn’t blow up on you nearly as often as the reputation implies. Just use good hygiene and make snapshots so if you blow it up, it’s only a 5 minute recovery.