for sure

When he was unsure whether to just make a pre-processor on top of C, or go for a full compiler (given that he had never created a compiler before), his mentors said, "full compiler, dude, go all the way and we will all help."

that's pretty bad ass if you think about it

new modern languages are made by people who took a compilers course and want to make a new langauge that looks cool and uses fewer semicolons

Sounds great, until there's no more funding and the language gets abandoned. Or the version you wrote all your software in, gets deprecated.

or the language isn't completely planned out and just becomes a total mess of unmaintainable half-implementations

Remember D? The "definitive C++ killer", by Walter Bright? Dude is really a genius with regards to compilers, but even he, screwed up and couldn't get it right the first time.

yeah I was actully really into D in the beginning and wrote a few little things in it

but stuff never really worked and pretty much anyone who ported interfaces for it just stopped

He created the first C++ compiler that generated native code (instead of compiling C++ to C), and proposed a bunch of details on the standard, to allow advanced low-level optimizations.

Return Value Optimization, Copy Elision, he invented it.

what do you think of Rust? I checked it out a few times but it was always a mess, and then all the sudden a bunch of stuff is being re-written in it and the head of the project is an insane SJW who's kicking people out who aren't trans minorities

Also, that's one of the things that made C++ a non-deterministic language.

Which makes Programming Language Design professors run away from C++.

that's a good point

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