![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
Adobe also recently snuck into their ToS that they could use whatever you made with their products for training AI and then gaslit everyone saying “we never said that” and changed their ToS. You know where you can’t access my stuff? In a cloud.
Adobe also recently snuck into their ToS that they could use whatever you made with their products for training AI and then gaslit everyone saying “we never said that” and changed their ToS. You know where you can’t access my stuff? In a cloud.
That’s about as far as I memorized it. What’s your method? I picture batches of 2 digit numbers on a number line.
Glad someone said it. Bugging me so much.
I really thought you were going to mention “Upload” on Prime. Same creator as the office.
Clearly we need Garfield in here then.
At work I have two monitors. One for input (my IDE for programming) and one for output ( the browser to watch changes for my react app).
At home I bought the 49 in. Samsung and have three monitors. Third is normally the log output.
It inserts the master changes before the task branch ones.
Kind of. Both merge and rebase result in the branches “synced up” but they do it in different ways.
Merge is making a batter for cookies, having a bowl for dry ingredients (task branch) and a bowl for wet ingredients, (master branch) making them separately and then just dumping the dry bowl into the wet bowl (merge).
Rebase is taking a time machine back to before you started mixing the wet ingredients, mix all the dry ingredients first then add the wet ones on top of that in the same bowl.
It’s really hard to create an analogy for this.
Merge is taking all the code from the master branch and combining it with the task branch, resulting in a commit for just the merge itself.
Rebase is “re-basing” where your task branch was created from off the master branch. It essentially takes all the commits from master that happened since you branched, REWRITES THE HISTORY of your task branch by inserting those master branch commits before all your existing commits, and effectively makes your task branch look like it was branched yesterday instead of like 4 weeks ago. You changed where your task branch originated on the master. You moved its base.
Atlassian does a fantastic writeup on this.
Not sure what that means. But you have workspaces that contain various tabs and you can’t access a workspace’s tabs from another workspace. I have workspaces for recipes, videos, programming, and gaming.
Workspaces. Vivaldi has this and it’s the only reason I use them.
Forget the headphone jack. Give me back my SD card slot so I don’t need to pay for your shitty storage for my own pictures.
The Dark Forest - no one wants to alert their presence or attract predators. Though knowing our Earth I think we’re stupid enough to do that. Cue the space lasers.
Cue the Republicans trying to ban HTML from our Internet to protect the kids. Yeah, you do that…
I’ve never seen a badge go past 999.
Excuse me sir, I don’t have any shit. Because of my bidet.
I hope you still have that thought when you are waiting for a torrent with 2 seeders and 40 kb/s.
I’m onto you FBI.
The sewer man came to me, with TEARS in his EYES, and said SIR, this is the best coffee in the world.
That’s like saying “we can cover this switch on the wall that will blow up your house so you can’t flip it.” I would feel better if the switch wasn’t even there. And now I’m wondering what other switches exist in my house that I don’t know about. The trust has already been shattered and I’ll never feel safe.