Comment on: With the news of Microsoft buying Github, I thought it'd be a good time to remind everyone that it's run by ideologically possessed SJWs
I give them 18 months in Microsoft's raving and ranting system. They'll create so much trouble, they'll get moved to the bottom of the pile and then ejected.
Much as I dislike MSFT, they're not that big on SJWism. Bing returns better results than Google, about the thing I use indirectly through DDG.
Comment on: Forcing women into programming is a fucking mistake
Whatever. Just don't fucking use underscores everywhere like a English lit major with a minor in Java.
Comment on: Developers that like new teschnologies tend to be bad developers.
Anything you can do in your latest shiny middleware I can do in K&R C and/or lisp.
One time we coded a Forth interpreter in asm/c to fit inside 8kbytes of firmware. It was cheaper in space to do that than code the whole thing in C.
Good times. I fucking hate modern IDEs.
Comment on: Awesome Modern C++ (Collection of resources.)
Did I say I hate C99?
I hate C99.
Comment on: Awesome Modern C++ (Collection of resources.)
Fuck C++. Fuck Stroustrup for creating that shitty language and fuck you for posting this shit.
K&R C FTW!
Comment on: ISO/IEC 14882:2017 - Programming languages -- C++ (it's released)
I was always on very slow shared machines. vi was the only option. Whenever I'd fire up emacs, I'd get beaten up. It seems strangely wasteful to be writing this on a four-core 32Gb machine.
Comment on: ISO/IEC 14882:2017 - Programming languages -- C++ (it's released)
DEC/Alpha but running VMS. Fast, but no vi.
Comment on: ISO/IEC 14882:2017 - Programming languages -- C++ (it's released)
IBM Mainframe, Apple II, a bunch of home brew 8085 machines, DEC, and then PCs and (real) UNIX machines for me.
Minix before Linux. Linux. Attempted to use 386BSD at home.
SunOS on 68030 (Sun 3, I think they were called).
I was there when Mach came out and didn't work. I marvel at the fact that IOS runs Mach and no one knows or cares.
Oh well.
Comment on: ISO/IEC 14882:2017 - Programming languages -- C++ (it's released)
58
Comment on: ISO/IEC 14882:2017 - Programming languages -- C++ (it's released)
The scary thing is, my code has probably impacted your life.
Are you on a smartphone or a laptop? My code is impacting your life.
The great thing about firmware is that it's everywhere and nowhere at the same time.
Comment on: ISO/IEC 14882:2017 - Programming languages -- C++ (it's released)
Gawd, I remember reading the draft versions of C++ when Stroustup was still writing them.
I remember thinking it was a crock of shit when I saw things like ++ is an l-value.
Never used it again. C was the best C.
Comment on: No, it is not a compiler error. It is never a compiler error.
Which standard?
I date back to the time when the production compiler was K&R 1st ed. and silly things like "void v(void) { void *vPtr;} had not been invented.
Comment on: No, it is not a compiler error. It is never a compiler error.
In thirty years I've found one compiler error. One. Something to do with the way the return value was handled in one register.
Something like this:
int f() { int result = a + b;
return; // instead of return result; }
It worked as the value was in the right reg anyway. Broke under recursion.
Can't remember the platform.
Fucking degenerates, everywhere. Infiltrating development now. It was bad enough with the zombies in HR and Marketing.
I remember this guy Steve disappeared in 1995 for a few months and came back as Sheila. Was transferred on its request to a different city altogether so as not disrupt the product group.
Now these fucks rub it in your face.