Isn't this exactly what reg.exe does already?

This can already be done.

Also, I hope they will keep the tabs on the bottom, and not clutter the titlebar with it. It's the window manager's job to draw the window border and decoration, definitely not the application's.

It seems "themes" or "branding" is the new fad these days. Is it so hard to just leave the window frame's look to be managed by the window manager, as it should?

I like my apps to look consistent. In fact, I usually take matters in my own hands when they insist on not doing it.

Folder windows certainly don't have their full path in the title bar by default.

I, for one, welcome our new hair-eating plant overlords.

Now I just can't wait for my TV to be owned by Flash exploits.

In other news, all Sun software will now start using 2GB of memory and being insanely slow.

Oh, wait...

From my experience, when filling forms that use carbon paper, there's no carbon under the signature area so you have to sign all copies separately.

I'd assume a carbon-copied signature would not be considered binding at all, and would be also be dead easy to spot.

You stupid hippie. Don't you realize that "rights" are just a mere social contract and nothing else?

They are not intrisic, and what we have created, we can destroy if we want to. That includes synthetic brains.

Without hormones, the "machine you" would feel no need to watch porn.

Same goes for any "survival instinct" you might have, of which "love" is a derivate. So at most, watching your grandchildren would be a pointless bore.

You are incredibly lucky you didn't fry anything.

Once you let the magic smoke escape, it's quite hard to put it back in!

Because there's no good way to make MSI's easily.

On one side, there are probably plenty of GUI apps to make MSI files. A basic one comes with Visual Studio, but you just don't have control enough over what it does. There's InstallShield too, but it's pay-for, and kinda heavyweight.

On the other side, you have WiX which attempted to be a scripting language to make MSI's, but that failed spectacularly IMHO. You have to declare in advance components, paths, files, and assign GUIDs to every single thing, it's a bother. Oh, and, all this, and you don't even have a GUI for your installer, just the "Please wait, Windows is configuring blah blah" dialog.

GUI support in MSI's seems to have been an afterthought.

And don't even get me started about trying to do it from scratch using Orca.

So, by the time I'd be done fighting with whatever restrictions the tool I'd have chosen would put in front of me, I could have whipped an NSIS installer script in 10 minutes with complete Modern UI and such.

May I suggest a few things to put in your .inputrc:

set completion-ignore-case on
set show-all-if-ambiguous off
Tab: menu-complete

Basically, this will make it act more like cmd.exe in the respect of completion: just type a few letters, then hit Tab until you got the filename you wanted.

bash's default behavior of beeping as soon as it's not sure annoys the hell out of me.