Carrots often have dirt caked on the outside that’s hard to get off with just water, so peeling is a good way to help with that.
The peel has the healthy bits
Sort of, but not really. The nutrients of a carrot may be slightly more concentrated in the skin, but all layers of a carrot contain those nutrients. You’re not depriving yourself of an appreciable amount of nutrients by peeling a carrot.
Those of pure enough heart to weild a Keyblade will know how to login - all you need to do is trust your heart, and follow the light!
Either that or they show up right as you sit down to take a shit, or while you’re in the middle of your shower
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.
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.
Just like any software design principle, it’s understood at a surface level by tons of bad developers who then try and solve every problem with that one principle. Then slightly better developers come along and say “ugh this is gross, OOP is bad!” And then they avoid the principle at all costs and tell everyone how bad it is at every opportunity.
anything we can do to push gaming into Linux would help it to become a better everyday OS
I feel like the SteamDeck and SteamOS have already done more for Linux gaming than ChromeOS ever had the potential for.
Sounds like he doesn’t want to spend his time tinkering, but playing.
Ehhh, I feel like this person is a tinkerer, it’s just the things they wanna tinker with don’t play nice with Linux.
Installing a modded version of Minecraft indicates a desire to tinker. Roblox is a game based around the concept of tinkering. EA games (especially ones from 7 years ago) require some level of tinkering even in Windows.
I get so many cloudflare captchas browsing on Firefox. They mostly go away when I change my user agent string to Chrome. Making the Internet more hostile for a particular group of users is pretty shitty behavior in my book.
He used to have some charisma lol. Also the early Linus Tech Tips content, like back when they were running it out of someone’s house, was usually pretty entertaining. Back then the content was much more silly and creative though, and much less corporatized.
https://www.allrecipes.com/article/should-you-peel-carrots/
Carrots are not like other vegetables