Message from @DanielKO
Discord ID: 464305445507432459
It's hard to prove formal properties of code that you don't know *exactly* what's going to do.
Honestly, when a company comes showing "here, we just invented a new language", I see zero value in jumping in early.
If one of the selling points is "it's like C++, but ~~with less features~~ simpler", you can be sure, they'll slowly add these features in later, and pretend they're innovating something.
right, the only reason I got into D was because of Bright and because of the familiarity of a lot of it
Rust I've done like hello world and some little stuff just to see what it was like
honestly what I dislike the most about Rust right now is the community
fuck any project with a CoC I'm weary of now
I started using Mercurial because Mozilla was using it. But I won't touch Rust.
In the early days of the boom of distributed source control, I went through Mercurial, Bazaar, one other that I don't even remember, everyone forgot... later git came about, I tried it too.
well Mozilla could have gone a totally different way if they hadn't chased out Eich
Monotone, that's the one.
never heard of Monotone
never liked Bazaar
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
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
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