I'm a chemical engineer and fullstack dev. Also not pissed, but it's worth clarifying that I am worse at frontend than backend...
BehindTheBarrier
joined 2 years ago
Made my own (windows only) to learn programming. Primarily because nothing beats Ctrl-C, Alt-Tab, Ctrl-V, Enter, Alt-Tab to download something. Then profiles, textfile with link support, and parallel downloads since some sites rate limit downloads.
Somewhat crude (don't ask me how the profile are stored behind the scenes, it's a mess)
That's true, i didn't think about that when I wrote it.
I'm used to the world being pretty simple though, so for me that slash has always just been a visual representation of the location of the branch if that makes sense. We don't have to have a slash in the branch name, only to use it to represent where that branch is located. It could have been something git only used for presentation.
I never considered branch names to be a vector, but in hindsight it makes total sense when put into a workflow like that.
What possibly surprised me even more, was that branch names weren't limited to basic characters or at least no special signs. I obviously see the case for all the extended characters outside the latin alphabet, such as Chinese characters, but I totally expected restrictions on special symbols like ", ', /, \, ;, etc.
It's said right in the article that games benefit from only using the main CCD (where half the cores are, those with the X3D cache) It's nothing new for dual CCDs to have overhead of splitting work across the two CCDs. So 8 cores makes sense here, especially when only one CCD has the "infinity cache".
The other thing is SMT being disabled. If I understand SMT, it's what gives the 2 threads per core. So maybe it should have been 8 cores, 8 threads in this case? Edit: I googled but didn't find a good answer apart from seeing someone benchmark the with the boost on, and the normal had the doubled core count threads, while the "turbo mode" only mentioned the core count (at half)
Thanks for the replies.
The stashing isn't as bad as it sounds, it keeps a copy around when swapping branch so even if you fuck it up, it should still be in storage. I think the worst one I had was popping from the shelf and it failed to apply but still got removed... I don't remember why that ended up happening but yeah. Not exactly related to the automatic stashing however. But I tend to more often want to keep changes changing branch than not. I have to use stash/Shelve less often because of it.
I know Jetbrains added a "all in one" diff option about a year ago, but I hate it as large/many files make it horribly slow and awful to navigate compared to just moving through the files one at a time. But the diff view itself good. I know there may be some that disagree, but it allows ignoring whitespace and newlines, which filters out non-important from important changes. For most programming (aka not python) whitespace changes means nothing so it doesn't matter 99% of the time. But it greatly improves going through a diff that had a total "code cleanup/reformat". Which is more often than one would expect in my project.
I asked about that for diffs, because I can't imagine using a terminal for this job. I don't mean any offense by it just to be clear, it's just not something that works for me. Perhaps I rely more on visual orgnaization. To give some context to that:
The standard way git shows up in a terminal (on Windows) it's diffuclt for me to "orient" myself in the code based on the diff, I prefer side by side diff compared to the split addition/deletion lines. I also like syntax highlighing that default git does not do.
Git in a Jetbrains IDE has the diff for any of my changed files is a single click away. The commit window has overview of changed files, a single click to view and edit a diff, including the normal syntax highlighting and one-click revert for a single change. Jetbrains specifically also avoid some of the bothersome part of pulling or checking out changes, as it doesn't force you to stash changes first.
Dealing with a merge conflict without a GUI also seems exessively hard. How do you do that through a terminal and keep track of things? Especially if it is a really messy conflict?
How do you view diffs and merges when you say you don't use git GUIs? External tool or terminal/command line?
I use Jetbrains IDEs and most of my life has been IDE based git interaction. And I honestly love it, easy access to see my diffs, the most common commit, push and stage(or shelve as Jetbrains does it, which is better than visual studio). Hassle free and available beats writing anything to me.
My own disks won't survive the house burning down, and while obviously feasible, aren't accessible when I'm not home. I don't need it often, but sometimes I do. But the extra safety of a cloud disk is nice.
The thing he wanted looks AI generated as well...
Just got reminded of the silencer gun battle scene in one of the John Wick movies. That was perhaps the most unrealistic thing I'd seen in those.
I don't think it will happen, and especially not for something this high profile, but Jury Nullification is essentially the "he did it, but we don't see his actions as punishable". It'd be a huge uproar if that happened too.