• 0 Posts
  • 22 Comments
Joined 5 months ago
cake
Cake day: November 25th, 2024

help-circle
  • Yeah I’ve noticed it sometimes seems to get worse. Don’t know what phone you use, but when I use Google’s voice-to-text on Android, I often have to correct mistakes, because it tries to do it word-by-word, but sometimes what I actually intend is not clear until I’ve spoken the whole sentence - and for whatever reason, Google very rarely goes back and changes a word it’s already transcribed. For instance, if I say, “I think your speaking” it’s not yet clear if that should be a “your” or a “you’re”, and it won’t become clear until I complete the sentence/clause.

    If I want to dictate a long piece of text, I will use OpenAI’s text-to-speech, which is almost flawless (it doesn’t start transcribing until you’ve finished everything you’re going to say). I appreciate some people don’t like OpenAI, but to be honest, Google isn’t much better, and likewise Apple is not a lot better than Google.


  • Well spelling was solved even earlier than that, with rote-learning at school in combination with the very environmentally friendly technologies known as the paddle and cane. What was wrong with that way of doing things?? Is it progress? Or were things better in the old days?

    In any case, all the words in the sentence in question are spelt correctly - the problem is grammar. Correctly determining if the grammar of a sentence is correct is a much harder problem than simply checking the spelling of words against a dictionary.




  • It’s a *lot* better these days. Here’s how you could use it to improve the English in your comment:

    Can you point out and characterise the grammar mistakes in the following sentence, with tips on how the writer could avoid similar mistakes in future - “I must admit its been a while, but all these things where horrible last time i played with them.”

    Sure — that sentence has a few grammar issues, each pointing to a common kind of slip. Here’s the breakdown:

    1. “its been a while” → “it’s been a while”

    Mistake: “its” is a possessive pronoun (like his, her, their), while “it’s” is the contraction of “it has”. Fix: Use “it’s” because the writer means “it has been a while”.

    Tip: When in doubt, try expanding “it’s” to “it is” or “it has” and see if the sentence still makes sense. If it doesn’t, you probably want “its”.

    1. “where horrible” → “were horrible”

    Mistake: “where” (a location) is confused with “were” (past tense of are). Fix: Use “were” to correctly form the past tense of “to be”.

    Tip: Say it aloud—“they were horrible” sounds natural, while “they where horrible” doesn’t. If it’s a verb (they were), you want “were”.

    1. “i played” → “I played”

    Mistake: Lowercase “i”. Fix: Always capitalize “I” when it’s a pronoun referring to oneself.

    Tip: This is more about habit than logic—just train yourself to always type “I” in uppercase, even in casual writing.


    Full corrected version: “I must admit it’s been a while, but all these things were horrible last time I played with them.”











  • MouldyCat@feddit.uktoLinux@lemmy.ml$HOME, Not So Sweet $HOME
    link
    fedilink
    English
    arrow-up
    55
    ·
    2 months ago

    fraid I generated a tl;dr for this rather verbose article:

    “Home directories are a mess because too many apps ignore XDG spec and dump dotfiles everywhere. The problem isn’t just legacy software—new apps do it too, often out of ignorance or laziness. Windows has similar issues with profile folders. Fixing it requires devs to actually follow standards, but many resist due to inertia or ‘my way is better’ thinking. Users should push back and demand proper XDG compliance to keep $HOME clean.”






  • The other posters seem to have bad experiences, so I’ll chip in with my more positive report @[email protected]. TBH I was expecting VR not to work all that well, but I was keen to try so I bought a second-hand HTC Vive, the very first model. Picked one up for €280 on ebay, which is a typical price or was two years ago.

    I was pleasantly surprised by how well most VR titles work. TBH I pretty much only play VR now. I always check ProtonDB before buying any game, which is a good idea in general but especially so for VR. The VR games I play most are Elite: Dangerous, Skyrim, Dirt Rally 2, Half Life 2 (a free VR mod is available on Steam), IL2 Sturmovik (a WWII flight sim) and Pistol Whip. VRChat works great as well. I’ve got a little way into HalfLife Alyx, but put it down because reloading guns in the dark is too much to handle whilst simultaneously being attacked by zombies with headcrabs. That’s not a Linux issue, just me struggling to remember the reload process under pressure. I have played a fair bit of No Man’s Sky, but performance is pretty awful. I’ll be trying it again after reading this news about improved support for it, but I’m not expecting much TBH as VR apparently has poor performance under Windows too. I’ve got about 5 or 6 other VR games which all work fine but just don’t grab me.

    I can’t think of any games that have issues - only thing I can think of is the free VR Labs “game” made by Valve, which has an “Item Shop” zone which has never worked. Every other part of it works perfectly though.

    Of course, the OG Vive is definitely showing its age, with a very noticeable screen-door effect - it’s like playing games in really low resolution. So I will probably upgrade soon - there have been rumours about a new headset from Valve - the Deckard - if that does make an appearance it might be my cue to reach for the wallet, because the other well-supported headset is the Valve Index, which is getting kinda old now (it’d still be a lot better than my Vive of course). Well, actually there is also the gen 1 Vive Pro.

    No other headsets have native support in Linux - you have to mess around with Monado or ALVR - this may well be why the other posters have had poor experiences. To reiterate, your best bets for VR on Linux are the OG HTC Vive, the gen 1 Vive Pro or the Valve Index.