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

help-circle




  • That’s not at all the argument I’m making. My argument is that English’s inconsistency is, at this point, the reason it is successful. By integrating everything into it, it has become a good enough medium of communication for almost everything. That would not have been possible unless the language eschewed consistency.

    Really, a better argument against changing the spelling is the classic “standards” xkcd, where now you’re just making another dialect of English where they spell words differently again, and now it needs to be adopted, fracturing the language further. Honestly, though? It doesn’t matter. Fix the spelling if you want. English can take the fracturing. The changes might take, they might not, but I doubt it’ll make the language more consistent overall, for every fix you put in, you’ll have someone who disagrees and doesn’t put it in, making your dialect more consistent, but the language overall less so, but it doesn’t matter. English will continue to be inconsistent, and that’s okay, that’s why it works.


  • The fool’s errand is trying to make the language consistent, when it never has been, especially trying to do it via spelling. English isn’t consistent. It’s not supposed to be. It takes pieces from every other language and integrates them into English whether it makes sense to or not, leading to inconsistency. That inconsistency, I think, is by design. It makes the language more versatile than any other, a “good enough” medium of communication for everything, but usually not the best, which for communication, tends to be fine.


  • To the spelling point: The world, for the most part, has moved away from the grammarian tradition of the 19th and 20th century of having a handful of dictionary makers decide what English is proper and what isn’t - the language evolves on its own, and if a misspelling becomes popular enough, it becomes a proper spelling. For example, facade is a french word, spelled façade, the accent under the C means it’s pronounced like an S. We dropped it in English because we don’t use accents in English, and now we spell it facade. It’s a “misspelling”, but you’ve probably never spelled it correctly. The language was never consistent to begin with, pretending you can fix spelling to make it so is a fool’s errand.










  • Heh. “Guy” has some interesting history. It originally referred to Guy Fawkes, because that was his name. Then it came to mean any person, gender neutral, then it became any man, now gendered, but the neutral definition never went away, so we have both meanings floating around still, but the original meaning, an effigy of Guy Fawkes, died.

    (I skipped a few steps in there because they’re not relevant between guy Fawkes and any person)



  • I really wanted Wayland to work for me. I just bought a new ASUS laptop (and ASUS has a great Linux compatibility track record, mind you!), 7th Gen Ryzen+Radeon, all AMD. I figured, let’s use Wayland on this one.

    I installed KDE Neon, updated the kernel (some stuff is broken on the LTS kernel, no big deal, easy fix), switched to the Wayland session, everything was fine…until I opened any chromium-based app. Crashed kwin, killed the session completely, it recovered, but in a new session. Switched to X11, everything works. Maybe if I grabbed a newer mesa from a PPA it would work, but:

    1. Crashing the window manager killing the session is awful and doesn’t happen in X11
    2. Chromium shouldn’t crash the compositor at all
    3. Even if it’s AMD’s new graphics drivers being buggy, that still shouldn’t kill the session!

    And I know, technically KDE could (and afaik, is) implement session management so that doesn’t happen. But to my knowledge, literally 0 WMs/DEs can recover the session after a compositor crash currently, and that’s a big deal.