ByteByteGo

Пікірлер

@themichaelw 3 сағат бұрын

2:17 isn't gRPC simply an implementation framework of RPC? The protocol could be something like protobuf, flatbuffers, cap'n proto, etc.

@cgarzs 4 сағат бұрын

Vertical video is cancer.

@maxspielberg6612 6 сағат бұрын

This was more helpful than i can explain. I am collaborating on github for the first time and didnt know what any of the differences were and just had a terrible day merging changes when i should have rebased. Everything makes perfect sense now.

@user-sh5bt6ze6n 6 сағат бұрын

The best explanation I watched!

@chiperror2441 11 сағат бұрын

You forgot Groovy smh

@laughingvampire7555 14 сағат бұрын

sadly for those that love the UNIX philosophy, which is against monolithic programs, monoliths are really the best choice for everything.

@jasonfreeman8022 15 сағат бұрын

This explanation is too simplistic. I searched for "git rebase merge conflicts". When commits D and E actually touch the same code files (and lines in those files) as commits A, B and C, there is still a need to do a merge. I rebase my branches and immediately get told that git is auto-merging and oops, there is a conflict in the file. I still have to merge (which isn't a problem per se). Then git rebase --continue and the rebase completes. Then I try to push and get told that I need to do a git pull. I do the pull and get a similar merge conflict. I fix it and a subsequent git pull works. Then I git push and it works. Then I generate a PR which shows dozens of files from other commits I didn't create on my branch. Whether this is a coherent explanation or not, there are things happening during a rebase that get glossed over. What is actually happening during a rebase other than simply repointing the branch?

@laughingvampire7555 15 сағат бұрын

so you don't know about vservers.

@laughingvampire7555 15 сағат бұрын

I remember those days and seriously, I prefer those days. docker is such an overhead