576
No AI* Here - A Response to Mozilla's Next Chapter - Waterfox Blog (www.waterfox.com)
submitted 10 months ago by to c/technology@lemmy.world
114 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 13 points 10 months ago (7 children)

very few who even touch AI for anything aside from docs or stats

Not even translation? That’s probably the biggest browser AI feature.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 4 points 10 months ago (5 children)

    Translation is my main use. Yes, the caveat that AI is 50/50 wrong is still there but at least I don't have to pester friends that know the language for everything. I only use it for unimportant things.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 8 points 10 months ago (2 children)

    To be fair, it's way better than 50/50, but of course no guarantees still.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 10 months ago (1 child)

    It gets the job done enough to understand the jist for me, yeah. But mostly I only do short posts. A language like Japanese makes it just a lot harder from what I understand from friends that learned the language. IIRC it's because the language relies on unspoken context and of course its grammar making machine translation trip.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 10 months ago (1 child)

    I only use it for unimportant things.

    The key to responsible AI use. Of course, in the grand scheme, few things are all that important.

    If the marginal cost of being wrong about something is essentially zero, AI is a very helpful resource due to its speed and ubiquity.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 10 months ago

    Similarly, translating from html/QML or js/py/rust is handy.

    Its still a pain because even good models like opus are hit or miss. The code still has to be reviewed and adapted. Can save time though.

    They are also very useful for mocking up a quick proof of concept.

    Is X doable? Will Y potentially solve the problems that my clients need me to solve? mock it up in two seconds with a few prompts and a language model and you don't have to take a stroll down a garden path.

    The actual work I still have to do but that's why I'm paid to do it.

  • permalink
  • fedilink
  • source
  • parent