Its an old pattern but it checks out. They do useContext now
Serdalis
joined 2 years ago
As a kid I loved that movie! Didn't even know there was a game, it reminded me of freespace.
I think the running theme has been that fern has built in stealth hax, since frieren struggled to find her before she could even suppress mana and the demon Lord couldn't detect her even using a flying spell right outside the window he was next to.
Also in the episode it looked like she was walking back to the two others as they were waiting expectantly and then she asks what now.
If the birds use mana as a threat reading above all else she could probably just walk over to it and pick it up.
Didn't she just pick it up cause she's super sneaky mana wise?
It's about economic damage, if they cost everyone else 1,000,000,000 in lost revenue, deployed assets etc, for the price of a few low cost missiles then they succeed.
I landed on boost for some reason and it reminds me of RIF so I'm happy but I'll take a look at the others too, thanks!
Dunno about others but I wanted my fix of random scrolling again after RIF died, tried the Reddit app and it was such a horrible experience it motivated me to actively look for something else, so searched for replacements and here I am.
Maybe others are doing the same.
They are simpler, but they do not scale. Eventually its better to create an internal package repo to share common code, this allows rolling updates a lot easier than a monorepo does.
Smaller repos are also less stressful for monitoring and deployment tooling and makes granular reporting easier which you will eventually have to do in large projects.
Simple for small code bases, a pain and a big code smell for large ones.
Edit: Some good discussion in comments, a good one to remember is that we are talking about the common case, in a common code base people will join and leave, parts of code will start becoming abandoned, in-depth knowledge will be lost. Its easier to keep track of and learn a self contained repo with a well defined boundry rather than a folder in a large repo with no well defined boundry and possible code leaching.
From experiance i would rather not have everyone elses mistakes and forgetfulness pollute my builds, tests and PRs and pulling a giant mono repo is much more of a resource hog on your dev system.
Having defined versioning for code packages was also a nice thing to have, specially with monitoring tools to tell you when a repo starts falling behind. You dont get that with a monorepo, even if you try and enforce some form of pseudo documentation for it, time crunch will slowly chip away at the correctness of it.