• 0 Posts
  • 37 Comments
Joined 1Y ago
cake
Cake day: Jun 13, 2023

help-circle
rss

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.


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.


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.




Not to “um, actually”, but I’m gonna “um actually” - technically, using git to host code in a decentralized fashion has been a standard capability of git since it’s inception. So it’s not really a new idea, just a new iteration


Listing those requirements up front would make things way easier for brute force attackers


It’s also a health nightmare. Beer and oil are some of the unhealthiest liquids you can consume (for different reasons, and in excessive quantities obviously), and having a functionality unlimited supply of them directly to your home would wreak havoc on the health of people with low self control or addiction issues. Like imagine an alcoholic living with the prospect of unlimited beer they could access at literally any time they wanted. That would be hell for them.


in a way that you can’t see what is going to be installed.

You can look at the Dockerfile and see every single step that goes into building a particular image.

It is also double resource heater.

That’s patently false.

And it has many frequent vulnerabilities

Dawg have you ever actually used docker?




I agree with you that Linux is not a drop-in replacement for Windows, unless literally all you do is browse the Internet. However, I kinda disagree with a lot of your reasons.

Yes windows blows ass, but everything still works on a functional level.

The reason I finally switched my gaming PC fully to Linux (PopOS specifically) was because my GPU drivers consistently crashed in Windows. They don’t crash in PopOS. Plenty of stuff doesn’t work or is hard to get working in Windows, but is plug-and-play in a lot of Linux distros.

You want to move over to Linux? Better backup ALL of your info onto a USB that supports Linux and Windows hd formats

Sure, but you’d want to back up all your important files even if you were upgrading Windows versions though. I remember when Windows 11 first released, tons of people ended up losing data or soft-bricking their machines in the upgrade process. OS swaps/upgrades are huge changes, and making a backup is the first step in any good OS installation guide.

you can’t use a built in troubleshooter

When’s the last time the Windows built in troubleshooter has fixed anything beyond the most trivial issues? Lol in my experience it was always next to useless.

Do I even need to get into gaming on non SteamOS distro’s?

Again, I game on PopOS, which is Ubuntu-based, and it’s been solid as a rock for over a year. I initially had some audio issues, but I was able to fix them with the UI, I never had to touch the terminal. Performance is the same if not better than on Windows, and for almost every single game I play, it’s as simple as clicking the play button in Steam. For the games where it’s not that simple, it’s usually either trying different versions of Proton, or checking protondb for command line arguments I need to configure in Steam. Both of these things just require drilling into Steam’s UI though, nothing on the terminal.

I definitely get where you’re coming from about the learning curve involved with the terminal. For the times you do need it, it’s daunting for an average user. Even if there’s tons of great documentation out there, it’s still overwhelming if you’re not experienced. But more and more is becoming possible with UIs - it’s getting more user friendly, and it’s not quite where it needs to be yet, but it’s come a long long way in the last couple decades.

As far as looking for replacements for Windows-only software, I feel that pain too. Just the other day on my Linux work laptop, I wanted to make a quick diagram in Paint, but I didn’t have anything preinstalled that I could use, and there were several graphics program choices in the software store, and I didn’t know which one to choose. I think this is ultimately both a good and a bad thing - more choices is almost always a positive, but again, it can get overwhelming, especially if you just want something now that “just works”.


I haven’t touched PHP since college, so about a decade, but back then I compared it to a very disorganized but well equipped toolbox. Everything you need to do your projects is there, but it’s scattered through 12 different unorganized drawers and cubbies, there’s an annoying mix of metric and imperial stuff, plus some random bits and bobs you inherited from your grandfather that you have no idea what they do.


I’ve only seen the first season lol. Planning on starting the second tonight. Apparently there’s a 4th and 5th season as well that I’m just learning about, so 2 and 3 must have gone well!



the ability to share models and interfaces between front and backend

On the other hand, this can be considered a downside because it locks you into using JS/TS on the front and backends.

Alternatively, if you define your models and interface with an Open API spec, you can write the front and backends in whatever language you want.


Also biologists: “vegetable” is purely a culinary term, and doesn’t have any significance in the world of botany


If you use a squash workflow, you’re going to be force pushing a ton.

Never force git to do anything. If you’re forcing something you’re doing it wrong.

This is bad advice. Better advice would be “know and understand your tool, and know the consequences of your actions”.


git rebase -i origin/main (or whatever branch you’re rebasing on), then read the instructions that come up in the editor window


In my experience, using GUIs is how people fuck themselves, and then I have to unfuck them via the command line.

Git’s interface is bad, yes. It has a step learning curve, yes. But I truly think the only real way to overcome those obstacles is to learn how git works, learn all the nitty gritty details, not hide from them.


The solution in this post is more complicated because it does more, and in an automated fashion, than your solution. Yours is simpler to set up, sure, but requires a lot of manual intervention to add content.

Once you go through the trouble of setting up the more complex solution, it pretty much takes care of itself, content-wise. It’s like your own self hosted Netflix/Hulu/Spotify/whatever else all in one.

Some people prefer your way, others prefer the more complicated way. I’m certainly glad someone has posted a guide, because either way I’m now aware of the steps involved and how big of an undertaking each solution will be, and can make an informed decision on which setup works for me.


Oh, I guess I was confused by your wording then. You said there’s no C flat or B sharp, but there definitely are both of those things. You also said there’s no half step between them, but B to C is a half step. I guess you meant there’s no note between B and C that represents a half step up from B or a half step down from C, but it wasn’t clear to me.


Well, there is a C flat, it’s just also called B. And vice versa for B sharp, that’s just C. There is a half step between B and C, it’s B to C. All the sharp or flat symbols do is signify you should play the half step up or down, respectively, from the decorated note.

The same is true between E and F. There’s a bunch of complicated reasons that the black keys have gaps between them, ranging from the physics of sound, to Western music theory principles, to ergonomics. I’m by no means an expert on any of this, I just think it’s interesting, and a fun topic to look stuff up about.


Why not just use a good language though?

You don’t really have a choice when it comes to front end web dev, JS is almost the only option for programming languages that run in the browser.