DoomBringer (aka fearmattdotcom, aka Matt) is a rabid Doom fan (I've played and beaten them all!). Other than that, Matt is a geek. He loves computer hardware and software. He is fluent in French, JCL, COBOL, FORTRAN, C/C++, C#, SQL, and Java. Other than computers, Matt does weightlifting, writing, and other stuff.
Why does C++ even exist? Why does MS keeps maintaining such a language that caused so many buffer overflows, and generally was not as secure as C# or Vb.NET.
Try writing a device driver some time, or say, a video game.
Yes, us C++ devs should just shut up and get to the back of the bus (and keep using VC6, who needs updates! I mean, improving standards compliance and new features are so confusing to us poor old C++ developers. We're dinosaurs, I swear, if it wasn't for
C++ I'd still be doing COBOL...)
In this situation, forget about global warming. They're saving money! Being green saves green. In more ways than one, really, as preventing climate change will save more money in the long run than not.
Nice timing, since I'm writing a plugin for outlook... (btw, which can really, really suck at points!)
It is far more difficult in Outlook to learn the object model, by tinkering, than it is in Excel. With Excel, you can record a macro, change some of the code, and run it. That process of interaction is very powerful. There is simply no comparable approach
There are many ugly parts. I've pulled many hairs out. But I have learned much.
All that managed stuff is nice, but has anything been done in native code (this is me commenting without watching the video)? I just finished a whole bunch of WM5.0 native code (there are several reasons for this...) and was curious.