Why browsers are bloated

https://github.com/WebKit/webkit/blob/master/Source/WebCore/platform/Scrollbar.cpp
https://github.com/WebKit/webkit/blob/master/Source/WebCore/platform/win/ScrollbarThemeWin.cpp
Let's reinvent the fucking scrollbar, which every goddamn platform with a UI already has, and make it behave subtly different from the native one!

Right-click a native scrollbar in some other app:
- Scroll Here
- Top
- Bottom
- Page Up
- Page Down
- Scroll Up
- Scroll Down

Right-click a scrollbar in Chrome:
- Back
- Forward
- Reload
- Save As...
...

Right-click a scrollbar in Firefox and Opera:
Absolutely fucking nothing happens!

What the fuck!? How did these terminally retarded idiots get involved in creating one of the most important pieces of software to the average user?

>>388
1. instead of having the compiler name in an executable file formats, just have compiled so it does not have any of that info. Making sure it is "generically" optimized.
5. Nope, you can remove __DATE__ and __TIME__ entirely, and just output a revision hash.
8.

They are in my binary when I compile with default gcc without using a RTOS.

Default, keyword there. Why I said you need to recompile using flags for more anonymity about it's source origin. Symbols can technically be done away with on any binary. Most flags and dependency calls can be anonymized too, by just the calling required hash of said Symbols and dependencies.

Even then, you are only identifying the binary with it, not the owner of the OS.
4. No, 2. The OS and distribution are always targeted for an architecture, always. If the binary has an OPcode from another arch it will horribly fail, even if you don't label the binary at all. You don;t even need to mark the OS and distribution, the binary will fail if it it's not running in the proper OS with it's dependencies. No need to mark the binary

Since most people use the default options or some popular options,

We are no most people, now, are we?

using most of the flags will make NSA know what binaries belong to a specific author.

Actually, if everyone is using the defaults to everything, it will make it worse for any intruder to distinguish it from another person that ran with the defaults. NSA included.

If NSA sees the "GCC (Debian 4.2)" missing they will know it's YOU and they will be able to find other binaries made by you.

And, that's the point of spreading a distribution, so that more than one person runs the same/similar system, making it difficult to distinguish it from others following your example. Why do you think people sharing files has done? Make one user more identifiable than the next by doing the same another has done?

if you use only fgetc instead of getc and getchar, they will try to connect it with other binaries that do that.

That's if you let the system poll the binaries in your system, like an improperly jailed system is (like those not jailed at all). Sure, being having a ``different'' scheme of binaries than the norm identifies you, but so does the simple MAC address or serial numbers of your device, which is the real threat to anonymity.

Also, try Cudder's Challenge: >>386
Simple raw binary, I assume assembled, not compiled.