The circuit board from an old IDE drive re-purposed as a networked device for controlling an irrigation system. Seemed obvious when I looked at it - after it'd been done. I/O, CPU, Flash, JTAG header, stepper motor controller - dirt cheap, tiny, low power, and built for harsh conditions.

Seems logical. And unlikely - for good reasons.

It's not psychosis - it's psychic abilities. Obviously.

You appear to be confused. That (wishlist) bug is not that Firefox can't or won't show plain text files (it certainly will, ftp, http, or local) - it's Add "View as Text/HTML/..." option for unknown mime content-type. As a typical /. reader I can appreciate how you missed reading the description or saw words that plain weren't there. i.e. conflated that with your claim that "Firefox will not render plain text files". Tricky.

The reason that hasn't been "fixed", and may never be fixed is because it's blocked by two other bugs (1 and 2). The main problem being that servers are unreliable when it comes to describing the mimetype.(in reference to your second sentence).

More importantly, as I've already pointed out - Firefox/Iceweasel does display plain text files

Rather than dismissing that fact, maybe you should have taken the time to read the link I posted on how to solve your "issue" (which works fine when the server provides the correct mimetype).

The relevant sections from the default mimeTypes.rdf (~/.mozilla/firefox/$gibberish.default/mimeTypes.rdf)

<RDF:Seq RDF:about="urn:mimetypes:root">
<RDF:li RDF:resource="urn:mimetype:application/pdf"/>
<RDF:li RDF:resource="urn:mimetype:application/postscript"/>
<RDF:li RDF:resource="urn:mimetype:application/x-bittorrent"/>
<RDF:li RDF:resource="urn:mimetype:application/zip"/>
<RDF:li RDF:resource="urn:mimetype:application/vnd.google-earth.kmz"/>
<RDF:li RDF:resource="urn:mimetype:binary/octet-stream"/>
<RDF:li RDF:resource="urn:mimetype:application/x-gzip"/>
<RDF:li RDF:resource="urn:mimetype:text/plain"/>
<RDF:li RDF:resource="urn:mimetype:text/html"/>
<RDF:li RDF:resource="urn:mimetype:application/x-mobipocket-ebook"/>
<RDF:li RDF:resource="urn:mimetype:audio/mpeg"/>
<RDF:li RDF:resource="urn:mimetype:application/vnd.oasis.opendocument.text"/>
<RDF:li RDF:resource="urn:mimetype:application/x-msdos-program"/>
<RDF:li RDF:resource="urn:mimetype:application/x-deb"/>
</RDF:Seq>
<RDF:Description RDF:about="urn:mimetype:text/plain"
NC:value="text/plain"
NC:editable="true"
NC:description="plain text document">
<NC:fileExtensions>txt</NC:fileExtensions>
<NC:fileExtensions>asc</NC:fileExtensions>
<NC:fileExtensions>text</NC:fileExtensions>
<NC:fileExtensions>pot</NC:fileExtensions>
<NC:fileExtensions>brf</NC:fileExtensions>
<NC:fileExtensions>srt</NC:fileExtensions>
<NC:handlerProp RDF:resource="urn:mimetype:handler:text/plain"/>
</RDF:Description>
<RDF:Description RDF:about="urn:mimetype:handler:text/plain"
NC:alwaysAsk="true"
NC:saveToDisk="true">
<NC:externalApplication RDF:resource="urn:mimetype:externalApplication:text/plain"/>
</RDF:Description>

Note: the order in which they occur is important. As is the presence of any other handler rules for text/plain.
If you have those rules, in that order, and no other rules about text/plain then plain text files will be rendered by the browser - I checked with Windows 8.1 (and I want that 10 minutes back).

If modifying/correcting mimeTypes is too hard for you. Use the extension that achieves the same outcome.

Agreed, pretty much. Though the key ones for my regular browsing are FlashBlock, NoScript and AdBlock Plus. The last two don't have complete replacements in Chrome. Note - we're only discussing personal preferences, not which is better. I recommend various browsers to others depending on their usage.

Chrome doesn't, yet, have equivalents for all the extensions I use for work.

Adblock Plus, CacheViewer2, cliget, Exify, Flashblock, GoogleSharing, Greasemonkey, Live HTTP headers, LocalLink, Modify Headers, NoScript, Print pages to PDF, RightToClick, User Agent Switcher, Add to Search Bar, Add-on Compatibility Reporter, Autofill Forms, Awesome screenshot, Browser Sign In, BugMeNot Plugin, CSS Usage, cssUpdater, Debian buttons, DNSSEC/TLSA Validator, DOM Inspector, Dust-Me Selectors, EPUBReader, Exif Viewer, Extended DNSSEC Validator, Firebug, FireDiff, Fireformat, Firefox OS Simulator, FireFTP, FireFTP button, Firepicker, FlashFirebug, FlashGot, Font Information, FoxGuide, FoxReplace, Google Plus Manager, GridFox, Groundspeed, Illuminations for Developers, iMacros for Firefox, JavaScript Deobfuscator, KDE Wallet password integration, New Tab Tools, Nightly Tester Tools, ODF Viewer, Open With, PageDiff, PageRank, Passive Cache, Password Exporter, QuickJS, RefreshBlocker, Saved Password Editor, ScrapBook, Scriptify, Self-Destructing Cookies, Server Switcher, TinEye Reverse Image Search, Video DownloadHelper, View Dependencies, W3Techs Website Technology Information, Wappalyzer, WCAG Contrast checker, YouTube ALL HTML5, YSlow

(from about:support, after a little sed, cut and grep).

Seriously?! Your install of Firefox won't render plain text files?? I've never had that problem and I definitely don't recall have to change any configs.

It sounds like either it's a Windows thing; you accidentally set the filetype handling behaviour; or you have installed a downloader extension that changed things. Take a look at your mimetypes. It's easily fixable.

Not having that problem here. It's Iceweasel but it should behave identically to Firefox. Lots of extensions. A five year old CPU and only 4GB of RAM. Two instances open (in different desktops) each with about a dozen tabs open. No freezes - ever.

Do you have Ad-block enabled? NoScript? (I find those two extensions tend to actually speed Firefox/Iceweasel up on many sites).

Have you tried Qupzilla?

Chrome (and Chromium) seem to be a bit quicker but not enough that I want to give up all the extensions I use.

Don't know how I feel about social sharing built-in - if I can't see it or notice it I probably don't care (I'll wait and see).

China does have some good points.

[puts on nationalist 'murican hat] It's probably just a propaganda campaign to make the USA look bad

[takes off hat] It's working.

I just looked up the manual - turns out he's right. The erratic use of scare quotes is proof of bi-polar. They look like bats "". Scary.

Bully for you. I quoted what I was responding to. And yes, you're still whining.
You seem to feel the need to lug the goal posts around while clutching at straws to build your strawman... meh, you probably need the exercise anyway.

I have no problems with people who don't want to use systemd, I don't use it for production machines myself (but apparently I'm a piss and kool-aid drinker). I don't like people who demand that choice be removed - and when the anti-systemd crowd complain it's not because they can't use their choice of init system. It's because they're fascists who want to deny others the choices they disapprove of. You know - like bullies.

Like you they attack anyone who isn't opposed to systemd - whether we actually use systemd or not. That's anti-choice, and bullying. You demand that developers don't use systemd. You demand the distros don't use systemd.

When people point out that you have no right to complain - you claim you're being bullied and that the alternative is unfair. What a load of bullshit. If you don't like it don't use it. If developers don't feel you are as special as you think you are, either: ask them nicely to reconsider (once) - bullying isn't going to work and name calling doesn't engender sympathy; do the work yourself instead of whining about how fucking hard it is; put the money up for someone else to do the work; likewise the neglected systemv-init - or just don't. Pick one.

In real life Open Source is not like some science fiction book you author - it's authored by others, and we don't do the work because someone, no matter how special they think they are, demands it.

I don't use systemd for work - but I do use it in projects I contribute to, and I will probably move to use it for work in the next year or two (when more of the bugs are ironed out). Because the existing init system is a poorly maintained unmanageable project and I have neither the time nor desire to help fix that - but you don't hear me whining, bitching, protesting, or pissing and shitting all around the place in protest and attacking and maligning anyone about it.
If only a tiny percentage of the energy the anti-system mob put into complaining and protesting was invested in work or other contributions to systemv-init - you'd have nothing to bitch about because systemd wouldn't be being built into to so many Linux distros. But that's not your point or you'd just be recommending other people who don't like systemd use OS/distros that don't rely on it - instead of recommending OS/distros that don't include the choice, ranting about urine drinkers, shit (speaks volumes of you), and systemd kool-aid. You know - quietly going about your business instead of acting like spoilt brat. A whiner. If you don't like it, take your ball and fuck off - oh wait.... it's our ball.