• 0 Posts
  • 130 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle






  • It’s a bit more complicated, really. The islands weren’t usually politically united. China lost actual control of the Ryukyu kingdom well before the first Sino-Japanese war, but maintained a claim on it for quite some time.

    The US took over administration during WWII and converted many of the Japanese bases to American ones. The US doesn’t claim any of the islands anymore and has closed some installations, but a lot of bases are still active. The US is responsible for Japan’s defense. Japan would rather have the bases in Okinawa rather than in mainland Japan (although there are a few bases there as well), which a lot of Okinawans feel is unfair. Okinawa is very well placed strategically though and Japanese people don’t like foreigners (sort of… It’s weird), so don’t expect the situation to change any time soon.

    BTW, if you ever want to visit Japan, Okinawa’s a great option. It’s beautiful there and it’s not hard to get by on just English.




  • spauldo@lemmy.mltoLinux@lemmy.mlWhy Are Arch Linux Users So TOXIC?
    link
    fedilink
    English
    arrow-up
    46
    arrow-down
    1
    ·
    1 year ago

    I’ve never talked to an Arch user about Linux, so I dunno how toxic their community is. But I do read Arch documentation, and it’s fantastic. Arch’s documentation has (for me, anyway) taken the place that used to be held by the old HOWTOs back in the early days.

    The kind of cooperation required to accomplish this doesn’t speak of a toxic community to me. I didn’t watch the video since I don’t watch YouTube on my phone, but I’m guessing it’s not the Arch community that has issues but annoying teenage “I’m more 1337 than you” jackwads that are the turd in the Linux punchbowl. Those little cretins are drawn to distros like Arch because they like feeling superior to the “normie” users.

    I should know, I used to be like that thirty years ago. Most of us grow out of it after we start getting laid.



  • Native Americans in what would become the US had stone-age tribal societies and oral traditions. It’s difficult to establish a consistent history for groups like that. To make things worse, by the time anyone wanted to make a serious unbiased attempt to document their culture, their culture had been changed long enough that no one alive remembered what pre-contact life was like.

    You might have better luck with Central and South American natives. The Aztecs and Mayans had written records, and the Incans left behind cities full of artifacts. Or check out the Inuit - they’re largely isolated so they had less of a change forced on them than the tribes living in more desirable areas.

    Or, depending where you are, you could always just seek out the local tribes and visit. Most of them have museums and books written by tribal historians and welcome people with a serious interest.







  • That’s cool and all, but why would I want to? Display systems are invisible when they work right, and X has worked right for me (save for some pre-EDID config issues) since the 90s. I run a program, it pops up on my screen and I interact with it. That’s all I ask of it.

    None of the issues I’ve had with X (drivers, mostly) will be resolved with Wayland. For me, it’s a solution in search of a problem. The only reason I have even a passing interest is that it’s (theoretically) easier to maintain and change as computing changes.

    I’ll move to Wayland when I have to, but right now there’s no reason to not use X.


  • I wasn’t clear. I meant that the issues with X crashing were usually driver issues. I have no idea about Wayland - I don’t use it since it doesn’t do what I want by design.

    X does the job well enough to be invisible to most people. Yes, we need a clean start in order to move forward efficiently (lots of assumptions about computer displays from the 80s no longer apply), but it’s good enough for most people’s needs.

    Why bother with a display server? Some people - like myself - actually use that functionality. It’s not part of the design for Wayland. Personally, I think that’s a mistake - especially as things become more cloud-based - but I’m obviously in the minority.


  • Wayland wasn’t the first attempt at replacing X. It has made more traction than any other attempt, though. There’s no real hurry - it’s not like X eats your babies and runs over your dog.

    As far as robustness goes, that’s mostly the driver. I’ve yet to see a bulletproof display system, commercial or non-commercial. If you cut out driver issues, X is on par with or more stable than other systems. It had better be, given that it’s had decades of bug fixes with few new features to cause new bugs.