• 4 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle
  • Not sure, but probably. I only used yarn 1. Never got around to trying yarn 2+ as migrating our fairly large monorepo project at the time felt like a pretty large and complicated ordeal. By the time I switched jobs npm was already a whole lot better in the ways most important to me.

    The little I’ve read about and used pnpm so far it seems a lot more plug n play than yarn while bringing big benefits. Even workspaces seems a lot simpler than it ever was with yarn (at least when I used it). Love the idea of non-flat node_modules and simplified lock files as well.

    Time will tell if npm incorporates enough of pnpm’s features to make it obsolete eventually but for now I can understand why it seems so widely adopted.





  • What I’m saying is that unlike other PCs the steam deck has very few varying factors (out of the box). Meaning, if it works for others, it is likely it could work for you.

    I’m not saying anything or anyone is infallible. In fact, I just had a look at proton DB and there are certainly plenty other people with similar problems.

    These are good news because Larian has a reputation for supporting and improving their games long after release. These kinks will get ironed out.

    And again, if you don’t wish to be an early adopter (which is completely fine), refund it.












  • burnso@lemmy.worldtoGames@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 years ago

    A couple suggestions:

    1. I’m no audio wiz but audio quality leaves something to be desired. Particularly, there are a lot of sharp “s” and some smacking sounds that I think some better equipment could improve. Might be as simple as getting a pop filter?

    2. Is there a public RSS feed anywhere? I don’t use Spotify for podcasts.



  • Thanks for summing it up! I get the point of the article a bit more clearly now.

    I wonder if “AI engineer” isn’t kind of superfluous in that case? It’s essentially just the new normal for software developers/engineers. Another API or tool to interact with to produce whatever product we’re building. Where does the specialist competencies come in, besides having a more intimate knowledge of the APIs and basic understand of how this tech works?


  • Interesting, but for some reason I found it very hard to read and get anything of substance out of the whole thing. Anyone care to help a dumb dumb out? Or is it just as fluffy as it seems?

    Also, is the newsletter any good? Or is it mostly speculative non-fiction with words thrown around that don’t really amount to anything?

    Don’t mistake my sarcasm for disinterest. I’m genuinely curious.