Well, if vim is for Real Men, and Real Men don't go to stackoverflow, why is there a vim question on stackoverflow?

You said it yourself: Real Men don't search stackoverflow.

What extra things?

Being able to skip to and fro with just the stroke of a key, and not having to navigate your way around different windows makes things easier.

Ah. Well, in that case that would depend on what font you use.

If you use a monospace font, the length will be exactly the same. Who uses times fonts in cryptography anyway.

Longer? How?

notepad is not comparable to vim.

To append something to the end of the line in notepad, you have to take your fingers off the letter keys. And you can't skip ahead or back a word at all.

Nor can you do :!make

With Tcl, I have only used Tk so far. I am not afraid of C++, so that is what I usually use with Qt, but I have used perl in the past (until I discovered that Tcl is a better perl than perl). I have dabbled with QML, but I don't feel satisfied with it.I am going to try python sometime soon.

That said, qtcl seems to be the usual bridge between tcl and Qt, so I would go with that. And probably will.

Both have applications that you might want that the other doesn't have. K3B, KDE Connect, Kontact, and Abiword, Inkscape, gucharmap. Among others.

KDE was first, and GNOME was initially started as a free alternative, for good reason that hasn't been relevant for a long time now. It was quite good until 1.4, and did a lot of things right, and was way easier on ressources than KDE. GNOME2 changed everything. It removed customizability and flexibility, and yet used more ressources than KDE2 or KDE3.

KDE4 has a bad rep because SuSE and RedHat released with the development version (unlike Debian, which stuck with KDE3 until KDE4 was user ready). KDE4's plasma is among the most lightweight (yet configurable) DEs, however some of the application back-ends are insane. Yet even with all the SQL and RDF databeses, it is less ressource hungry than GNOME3.

GNOME3 seems to have begun as a re-write of GNOME2 to be more Mac-like, but recently seems to emulate Unity instead. Meanwhile, KDE5 has become even more responsive and light-weight than KDE4, but is still not fully user-ready, so I can't recommend it (yet).

The biggest problem with GNOME currently is GTK3, which strips features that RedHat doesn't need or want, despite app devs and other DEs like XFCE relying on them. LXDE has begun the switch to QT because of this, and the diving application SubSurface has improved greatly since doing the same. The problems with GNOME and GTK in general are made worse by cyclical build dependencies that should remind everyone of Ken Thompson's Reflections on Trusting Trust.

Finally, Qt is simply a joy to work with. It is C++, yet feels like a completely different language of its own. GTK is awkward by comparison. I'd also argue that Qt is more portable that GTK, but that depends on what you do with it. I do want to mention KDE's Smoke libraries which offer bindings for languages including python and JavaScript.

All that said, I do most of my GUI stuff with Tk.

I used to write firmware, too.

#include "pins.h"
#include "uart.h"
#include "systime.h"
#include "sysinit.h"
#include <stdio.h>
#define BAUD 115200
int main(void){
    init_pins();
    systemInit();
    initSysTime();
    uart0Init(UART_BAUD(BAUD), UART_8N!, UART_FIFO_8);
    while(1){
        iprintf("init success\n");
    }
    return 0;
}

You can't bullshit me.

-Os; everything else is snake water.

To me it doesn't read like fascist garbage; it reads like a list of reminders by the author for the author.

Types: On ARM, char is signed unless declared unsigned. On Intel, char is unsigned unless declared signed. Either way it is 8 Bit, and so is UTF-8. I have to agree that types, even if equivalent, should convey intention, if only for the benefit of maintenance. Then again, the elegance of C is that it has only about 20 keywords, from which you can build anything but self-referential structs. I like to keep things small and simple, but I trust the compiler to optimize human maintainable code.

I'll use long and short where I need 32 and 16 Bit types, and int where size doesn't matter and byte should be enough and I trust the compiler to put it in a register only. Most for loops, for example. I know int is long these days; I don't care. The compiler should be free to use as int whatever the CPU is most comfortable with, and that is what I use it for.

I may be persuaded to use int32_t for short, but I really see no advantage in it. (I really wouldn't mind a byte keyword to supplement char, if only so the strlen of a character array can intuitively reflect something other than the number of bytes. But that is basically syntactic sugar, and I should watch my weight.)

Return types:

if(!array=realloc(array)){free(array);array=NULL;}return array;

"Do not do this." No shit! How about a gore warning? Children might be reading this! Horrible!

All in all, a useable write-up, though I should expect most people here to be already familiar with the content.

WTF?

What do you propose? string[]? Fuck your OOP mindset.

what is the environment that needs this 0? fuck off!

Do you even script?

Seriously: How do you build commands from simpler commands if you can't check for error conditions?

Are you even a programmer, or do you just click together GUI stuff?

Use clang.

Don't use the mouse. Install Cygwin.

Example: pdfseparate, part of the poppler-utils, will split your PDF into single files or extract specified pages.

You can automate anything on the command line, and have it run in the background, interactively, non-interactively, parameterized. You can even combine what you have automated to automate using your automations.

http://www.tldp.org/LDP/abs/html/

TL;DR: Nothing, ask your devs.

Apart from EasyScreenCast and ShellShape, all the functionality of those extensions is part of a stock KDE, which is why I don't understand this sentence:

Some monsters like a KDE is not a bad choice if you “need more”

KDE has less memory footprint than plain GNOME.

Another issue is that in the past GNOME extensions have stopped working after upgrades. How many of these extensions will still work in a year?

Some of these extensions seem to only re-create features that were removed from GNOME.

He is the manager.

Android is an official Linux OS.

With commercial software people are told to fix the bugs, "or else".

Actually, I was told not to fix bugs because it would take too long.

With open source software people do whatever they like and ignore unrewarding bug fixes.

Do you want forks? Because that is how you get forks.

The reason why the Linux Kernel is not a total failure is there a lot of corporate money being invested making the Kernel work.

Actually, no. Most bugs happen in the corporate code contributions, which are made because of Linux's success, not the other way around.

Did you know you can send git pushes by mail?

git format-patch

https://igurublog.wordpress.com/2014/02/17/biography-of-a-cypherpunk-and-how-cryptography-affects-your-life/

You think that is how bad it can get? Monitoring all online communication, blocking foreign web sites, personally discouraging cryto-hackers? Imagine what they could do if they controlled all of the DNS root servers!

Hawking's speech system sounds just like my Amiga500.