146
Open Teams in a mobile browser and Microsoft says your browser is unsupported and to download the app, but if you request the desktop site it works (lemm.ee)
submitted 1 year ago by to c/assholedesign@lemmy.world
27 comments fedilink hide all child comments
 

Of course it looks like shit though. It doesn't size to your screen, it looks like normal teams but really small.

Outlook works in the browser fine, and maybe I don't want to have teams on my personal phone but occasionally want to check things

you are viewing a single comment's thread
view the rest of the comments
[–] 0 points 1 year ago (2 children)

Building llguidance, multi architecture, and all supported back ends.

Do you always act like such an asshole to random strangers by personally insulting them, or is it just when there are no apparent peer pressure consequences from people in your daily immediate surroundings. Some humans are physically disabled in involuntary social isolation due to the actions of others. Imagine you were such a person on the other end and had this kind of interaction in your only human contact outside of a bedroom prison of a life.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    Good for you. And no, I am treating people offline and online pretty much the same.

    You should reflect on your initial comment and how that set the tone for the conversation. You claim llama.cpp to not be open source. Well it is in every definition even if it depends on proprietary software. Which it does not necessarily need to as it is fully compilable without cuda, etc with just the CPU inference Backend.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 0 points 1 year ago* (last edited 1 year ago)

    It is the CPU back end that is giving me trouble with build all. The free as in freedom aspect of open source is violated when any software promotes and primarily supports a proprietary tool chain. Things like how there are two checklist files, one in the primary and one in the build directory likely prevents many from succeeding. If the initial configuration was wrong or needs to be changed, the user will likely attempt to change the checklist in the main directory only to find that the changes do nothing. Several of the back ends also require manually tracking down their library paths and adding these to the source. Many of these, such as BLAS, CuBLAS, and Vulkan will fail until just the right version is included while the errors have no hinting. There are numerous other issues like ARM options not described as such, and ambiguous runtime options. Various edge case options generate a fatal warning error. Once any of these are set, the build fails without hinting about the cause, and the barely mentioned solution of manually editing the checklist yields no results.

    I'm sure this is trivial for the average dev, but dev I am not. I'm just some weird script kiddie that can also build an ALU with a NOR gate, or might talk about a 65C816 in a room of 6502 fans. But I have a large number of other interests in life.

    Be nicer to people. When some dumbass takes 8.5 of your 9 cat lives on the road one day, cordiality can have a large impact on your daily. I was much the same to others and regret it.

  • permalink
  • fedilink
  • source
  • parent