Exactly.

used Mercurial for a bit, but Git went crazy and I'm so OSS it seemed silly not to just go full git

we had an SVN sever before that which shit the bed on us and we had to completely re-assemble a really messed up code base

I'm more of a Free Software guy.

Monotone was supposed to be good because it was fast, written in C++. But it turned out Mercurial was virtually just as fast, because most of the time was spent doing I/O, and they did some tricks to optimize I/O.

honestly after coming from SVN speed was never so much of a consideration

if it was faster than SVN it was fast enough

Speed matters if you're dealing with a massive project, and your workflow requires switching between branches, or rolling back and forth between revisions to locate regressions.

That is, if you're Linus Torvalds.

we're a small team and we work with pretty tight feature branches, so that would rarely be an issue for us

If you're a kernel developer, you wake up, there are 20 new patches/pull requests since last night, waiting in your inbox, for you to review, apply, test. You'll spend most of your morning checking if they conflict with each other and rebuilding to test things. Probably the source control management takes half of your morning.

yeah, for sure, and I think that also describes a lot of how git is designed

doing that in SVN would be torture

https://www.youtube.com/watch?v=FnGCDLhaxKU

I'm watching this. Quite interesting, on how LLVM does some optimizations.

"Const methods and const references play no role in the LLVM optimizer."

this guy's talks are typically pretty good

Trying to help out on a node project and it's using "knex" to build DB queries. I have no idea why anyone would use this, the code is literally longer and more complex than just a raw sql query. It doesn't even completely abstract database types like a proper ORM would.

seriously why is the JS world so full of shit

Because JS programmers.

JS web apps are the reason humanity deserves nuclear annihilation

radical Islam > JS

I should become an imam and declare a jihad on using unmaintained node packages in production software

https://youtu.be/s4wnuiCwTGU

Best followup talk.

I'll watch that in a bit, that looks good

LLVM can do up to 3 inline optimizations, and he still doesn't know why.

... huh

runtime overhead limit?

no

huh

He can manually control the optimizer passes to convince the compiler to do a 4th inlining.

The optimizer is derived from something I assume

Clang is a front-end for LLVM.

ah

He's not a LLVM programmer, although Clang is their most important front-end.

I mean, he's not responsible for LLVM itself.

back when I did embedded stuff we would mess with the runtime to create different runmodes, and we did stuff like made generic unrolled loops for rasterizing and we'd put them straight into the runtime

so basically to do a draw cycle we'd use a DMI call to switch runmode

for some reason that came to mind just now but thiking about it there's absolutely no way that's how clang is doing any sort of optimizaiton

*incomplete thought - the crt had a size limit so in my head optimized code + limit to 3 connected to that