It makes sense to me, we're talking about a highly addictive psychoactive substance. It's much harder to get out of addiction than not get addicted in the first place, and people born after 2008 did not have a legal way to get addicted yet. That's exactly how I'd approach having a transition period to not cause unnecessary suffering in the process.
More like a custom which sometimes has good reasons to be broken than a golden rule. A branch in Git is nothing but a pointer to a commit, anything more than that is social agreement that can differ in various contexts.
Yeah, I've never used Jujutsu, but from what I've seen so far everything it does can be done with Git itself, just perhaps in a (sometimes significantly) less convenient way.
Sure, true, I would say "often significantly" though, to the extent that you would never bother doing half the things with git that you can do with Jujutsu because it's such a pain.
Some will say that it's a "red flag", others will say that those saying it's a red flag lack the experience of working on diverse set of projects with various needs and requirements.
> Some will say that it's a "red flag", others will say that those saying it's a red flag lack the experience of working on diverse set of projects with various needs and requirements.
What if those who call out red flags actually do so based on experience,particularly in understanding how and why red flags are red flags and why it's counterproductive to create your own problems?
I mean, if after all your rich experience working on diverse set of projects with various needs and requirements, your answer to repeatedly shooting yourself in the foot is that you need a tool to better aim around your toes... What does it say about what lessons you draw?
"Merge 2 branches" is already far from being a primitive. A git repository is just a graph of snapshots of some files and directories that can be manipulated in various ways, and git itself is a bunch of tools to manipulate that graph, sometimes directly (plumbing) and sometimes in an opinionated way (porcelain). Merging is nothing but creating a node (commit) that has more than one parent (not necessarily two) combined with a pluggable tool that helps you reconcile the contents of these parents (which does not actually have to be used at all as the result does not have to be related to any of the parents).
(you may know that already, but maybe someone who reads this will find this helpful for forming a good mental model, as so many people lack one despite of working with git daily)
Framework is perhaps well-documented, but it's not open. There are only pinouts, partial schematics and some MCAD stuff published for extension development but no ECAD designs.
They're pretty good, but you can find other good trackpads too. The main thing about Apple is that their trackpads are consistently pretty good, while with other brands it can be hard to figure out what you'll be getting until you try it yourself.
There's also software component. It has improved by now, but early libinput was giving some good trackpads bad rep.
What makes you think so?
reply