Diff: [root] @ 85324b47415 | faq | css

wbmd update

File: web_browsers_must_die [Diff]

diff --git a/web_browsers_must_die b/web_browsers_must_die
index d3ec095..969deac 100644
-- a/web_browsers_must_die
++ b/web_browsers_must_die
@@ -8,21 +8,15 @@ Let's look at those:

h2. Typical features of a Web Browser

h3. JavaScript/AJAX JavaScript support

!http://dump.bitcheese.net/files/jycymew/noajax.png!

Useful in very rare cases. Mostly used for abusing user computing resources for sake of distasteful eye-candy. Also, all the browsers support it with specific glitches, so so-called "frameworks" are required to make more or less complicated code work in more than one browser. These "frameworks" take up hundreds of kilobytes, and different methods of code compressing & obfuscating are employed to make it not so fucking slow.

Good example of JavaScript failure is recently released Google's "Closure":http://code.google.com/closure/ tools. These include:

* Perfectly bloated "JS library":http://code.google.com/closure/library/, with custom-drawn, stoned slow widgets, WYSIWING stuff, spinning, whistling and farting stuff and unit testing for digging in the shit in more comfortable way.
* Apotheosis of JS downfall: "Closure Compiler":http://code.google.com/closure/compiler/! So much for interpreted language: you still have to compile *before* you deploy to get good performance. It also includes some kludges for JS, including obfuscated code debugger (that reminded me of recently-released fixer for executables) for Firefox.
* "Closure templates":http://code.google.com/closure/templates/ — rather harmless tool, which allows to load user PC even more by processing templates, to unload server, that's busy running bloated Java/Python crap.

AJAX. The worst thing that happened to web ever. While JS can abuse your resources locally, with AJAX you can get into a fucking botnet with webpage living on its own.

Things that can be done in AJAX: JavaScript:

* Drawing shit all over the page
* Drawing shit with non-standard navigation all over the page.
@@ -30,7 +24,7 @@ Things that can be done in AJAX:
* Spinning, jumping and beeping shit.
* Turning nice, informational, stateless webpage into fucking self-aware crap, i mean, web application.

AJAX interfaces inherited Flash's poor navigational qualities that led to its downfall (see below). It's positioned as cross-browser, plugin-less replacement for it, but doesn't work this way (see above).

HTML is being transformed on the fly with AJAX, like it was a data structure. But it isn't! It's a markup language. It can be malformed, and browsers can't reject it: the browser that displays most pages wins. They try to fix it, while breaking it even more with JS scripts, this leads to even more horrible mess.

@@ -50,7 +44,7 @@ h3. Ad/flash/JS (sic) blocker

The reason for those (mostly) is to get rid of JS/Flash crap hanging from low-class sites, that gets in your way, slides from sides, hovers the text under your mouse, etc. If you get rid of user-side scripts, you deal with them all at once. JS-less advertisements can hardly do more than aggressively blink. If you don't like advertisements, don't visit the site. You only make them more profittable by doing so. If you need information *that* much, so you absolutely must have it, well, ads are the price for it.

Reasonable ads, like Google "AdSense":https://www.google.com/adsense/ are not distracting and usually well-separated from content, so why bother blocking them? However, if you wish to block such honest ADs, ads, you can easily do it by blocking certain host in /etc/hosts*. More blocking can be done on proxy-side, like using "Privoxy":http://www.privoxy.org/. This solution does not perform vendor lock-in like browser plug-ins do.

h3. Password manager

@@ -58,20 +52,21 @@ Well, that one deserves to live, not in that form though. Instead of inputting y

h2. Browsers post-mortem

"IE":http://www.microsoft.com/windows/Internet-explorer/default.aspx — Was great once. Then its developing stalled, and others easily outrun it. Typical insecure MS crap as of today today, and MS keeps peddling it to the tune of "This time, it really works!".

"Firefox":http://www.mozilla.com/firefox/ — bloated crap that was thrown out to OS open source community by Netscape, when they lost any hope of beating IE. Unfortanately, it's still alive and was on its way to vendor-locking web in on itself, taking place of defeated IE. Then Chrome stepped up.

"Opera":http://www.opera.com/ — It's not really a browser, it's an Internet client. It features crappy BitTorrent client, awesome IRC and mail clients, and some mad stuff like "Unite":http://unite.opera.com. However, its HTML engine is used to be quite good. Lost to Webkit.

"KHTML":http://en.wikipedia.org/wiki/KHTML based — the most awesome HTML engine so far. Light in memory (compared to others) and displaying HTML correctly. Also, it supports JS, and quite good; Even 3.5.10 did support enough of it (to run a simple onclick(), for which JS is only good for anyway) though.

Browsers include: konqueror (see very below), rekonq (shit).

"Google Chrome":https://www.google.com/intl/en/chrome/browser/, "Safari":http://www.apple.com/safari/ and other "WebKit":http://webkit.org/ based: based browsers: this engine is basically pimped-out (by Apple) KHTML, then maintained by joint force of several browser vendors which is somewhat better than Firefox's Gecko. The most reasonable engine so far.

Notable browsers:

* Google Chrome: well-maintained "giant kludge":http://bitcheese.net/art_thou/bow/chrome.html. It doesn't really get a lot better when you're dealing with modern web.
* "Safari":http://www.apple.com/safari/ — not bad for casual web browsing, even on iPhone.
* "uzbl":http://www.uzbl.org/ — These guys got UNIX philosophy all wrong. Their browser does all the complex shit like AJAX anyway. You can tamper with interface and some stuff like bookmarks or cookies though.

@@ -81,7 +76,7 @@ h2. Reasonable replacement

Universal document viewer, like "Konqueror":http://www.konqueror.org/.

It features viewing all kinds of documents (like PDF, images, texts...) over not only HTTP, but any protocol implemented. It uses KParts (embeddable document viewers) and KIO-slaves (plugins for accessing different protocols) and ties them together to make a truly universal "browser". It doesn't implement anything itself, but hosts reusable pieces of software. Also it features unified means of authenticating (KWallet), suppling cookies (for HTTP), which allows to strip Web of its hyped-up uniqueness and erase border between local and web browsing. Unfortunately, it's unmaintained: KDE4 version lacks some important features and is buggy, while KDE3 one is still awesome as hell, but only useful for browsing well-written sites like this one, which are a minority.

h2. Ideal replacement

By Voker57 on 2013-12-02 13:01:50 +0400 Powered by bitcheese wiki engine