The State Of GNU's GDB Debugger In 2016

[gilboa]

Well played!

- Gilboa

[gilboa]

How Red Hat took over GCC. A guide:
1. Write all your commits as C++like C and push them upstream over a course of 5-10 years.
2. Wait until all sane maintainers leave (February 2015).
3. Say, "Hey, it's all really bad C looking like C++! Let move to real C++!".
4. Behold: Only your Red Hat devs can maintain GDB\GCC properly.
5. Profit? Nope. People saw C++ coming and figured if they're going to swallow that bitter pill, they might as well do it with CLANG.

Now, moving on to the linux kernel...

You seem to have a very solid, yet unfounded and completely ridicules idea on how open source and open source maintainer-ship works.
1. Guess what: If RedHat employees are brave enough to maintain gdb, they get to decide which programming language is used to develop it. Those who disagree can fork, rewrite or simply shut-the-***-up. Contrary to popular belief, OSS is not a democracy, its meritocracy. Feel free to Google the term up.
2. Even though I'm a C kernel / system developer by trade (kernel code in C, user-land in C++) and even though I greatly prefer C over C++ (Easier to write *clean* OO code in C) you failed to back up your rant with anything coherent - as in, why C++ is inferior when developing a debugger.
3. Care to offer an alternative? Are you stepping up and offering to maintain and develop a clean C-only GDB?

In short, troll much?

- Gilboa