Then teach us. Advocate for us. Help us improve and understand.
A very large part of the problem is that the people who are knowledgeable are often the ones that bought into the whole lone wolf coder shtick.
Most junior people I work with are interested and want to learn, but between high demands, no time to do it and senior devs who focus only on their own problems - it’s very hard to know how to learn and improve.
We can and need to solve this but it requires that we work together and actually sit down to bridge the knowledge gap.
Honestly couldn’t care less. But if that means more Jak & Daxter games then go ahead.
I wonder of this will also apply to npm then. I have a package that uses private packages which requires a personal access token to be present in env. Would make for nicer DX in our case.
You do you, friend. I’m not trying to defend anything, just trying to help you out.
If you want to go on a crusade against anti-consumer practices or whatever then requesting a refund seems like the first step.
In short:
🤷♂️
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.
Why not help build it though? It’s all community driven and unlike Reddit, Lemmy is much better at surfacing small communities and new posts. You’d be surprised how quickly you can get replies/comments.
How does the original hold up? I’ve heard good things about this game and have always been a little curious to try it.
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.