Palworld is an open world survival crafting factory/base building game, that happens to borrow the catching mechanic from Pokemon (who borrowed it from Shin Megami Tensei).
Palworld is an open world survival crafting factory/base building game, that happens to borrow the catching mechanic from Pokemon (who borrowed it from Shin Megami Tensei).
You think it’s unreasonable for a software developer to take one to two days to learn a tool that’s basically ubiquitous in their field?
What I do locally on my branch is my own business.
Lol ok, but don’t expect git to read your mind. Like I said earlier, if people take a day or two to understand the tool, they can adjust their personal workflows to work better within the confines of git.
I don’t think rerere
applies here. Once you do a rebase, the rewritten commits should contain the conflict resolutions. The only way conflicts could reoccur on subsequent rebases is if changes reoccur in those same files/lines.
Only if there are changes in the same files and on the same lines in both branches. And if you’re a commit freak, you should probably be squashing/amending, especially if you’re making multiple commits of changes on the same lines in the same files. The --amend
flag exists for a reason. No one needs to see your “fixed things”, “changed things again”, “fixed it for real” type commits.
That could happen if the base branch has changed a lot since the last time you rebased against it. Git may make you resolve new conflicts that look similar to the last time you resolved them, but they are in fact new conflicts, as far as git can tell.
Neither rebasing nor merging should cause trauma if everyone on the team takes a day or two to understand git
Look, it’s fine if you prefer other languages to python, I won’t besmirch anyone’s preferences. But literally everything in your post exists in nearly every programming language (minus some of the typing stuff, I’ll give you that, but it’s getting a lot better). Like, every language has some learning curve to setting up tooling, or configuring your IDE the way you like it, or learning how to navigate documentation so that it’s useful, or trying to decide on one of the multiple ways of doing things. I guarantee, as someone with limited experience with Java, I’d have a difficult time setting up and using IntelliJ, and figuring out which build/packaging system I need to use, and figuring out how to use whatever libraries I need, simply because I’m unfamiliar with the ecosystem. That’s all you’re describing - the initial learning curve in getting familiar with a new language. Which is why I pointed out all the things I pointed out. It’s where I start when I’m introducing developers to python.
Yeah playing quickplay in Overwatch has all the sweaty counterswapping and flaming for off meta picks as competitive, except with a 5-10 minute queue time instead of 20-30
That feels like a packaging issue, which would be a problem specific to the developer of that app, not Python. For the most part, pip packages install basically instantaneously.
especially when u are indenting stuff inside stuff with a bunch of conditions everywhere
That’s an anti pattern in basically every language though. The fix is to simplify those conditionals, not use a curly-bracketed language.
If you need any kind of libraries
PyPI has a huge selection of libraries
assistance from an IDE
PyCharm a super powerful IDE, VSCode has tons of Python extensions that L rival PyCharm’s functionality, lots of other IDEs have decent python support
or a distribution build
Not sure exactly what you mean by this
or you’re more familiar with another language
Yeah this can be said about any language. “You’re quickest in the language you’re most familiar with”. That’s basically a tautology.
Copying would imply a one to one duplication. The catching system in Palworld differs in multiple ways from the Pokemon system. I think that’s enough to call it borrowing and not copying.