Monday, February 16, 2009

Bleeding Edge should be an option, not a competition

Re: [ PPLUG ] Tropical Ice Cube Newsletter #7: A Flurry of News!
From: "Jean-Philippe 'Tropical Ice Cube' Monteiro"
pplug ::at/
Date: 09/02/16 - 19:08

On Monday 16 February 2009, j. Tim Denny wrote:
> Jean-Phillipe
> seems you are really down on Ubuntu in this news letter? what is wrong?
> chat?
> cheers
> tim

Hi Tim, Ye Chanpion of Looong Threads here on our PPlug planet!

Old story between me and U - I'll put it down to the famous motto: "Linux is all about Choices" - When one distro is on such a World Domination Rampage, the future just looks gloom again. And in this case, a rather brownish shade of gloom, which doesn't help at all.


The long-ish answer is that progress has never meant "Better"; it just means "Different" in all aspects of human life.

it's the same old story:
A hundred years ago, there where on traffic jams, it was so better
A hundred years ago there where no ambulances, and that sucks.

[The first one to say that a hundred years ago you could be at the hospital faster because of the uselessness of ambulances in traffic jams is to me a very healthy individual, thank you!)

And so it goes with software; once Linux was blazingly fast on your 256megs of ram old laptop, and 2 years later OpenOffice takes a full minute to start, crashes and do not recover stuff because the RAM is overcrowded, you aging old 5400rpm IDE swap disk stuffed... Not mentioning that your trackpad module was dropped in the meantime, deemed obsolete, and your only solution is to stick with an unsupported, outdated distribution that you can't really maintain...

The Benchmark Story in Newsletter #7 is true, and I don't care much about Mac OS X results since they run an X server too, and they do push upstream lines of code to the BSD project - which is more than what Ubuntu does, since U recipe for victory is to attract, and keep attracted in the halo of it's brownish, t(h)ree-hugging warm light a maximum of individuals who would contribute to U rather than push stuff upstream. And U doesn't fix the kernel, U patches it for it's own use, that's all.

The above is only my post, but if you read upwards, someone like me suffered a regression in hardware support. Slackware's boss, P. Volkerding, said it: WHY FIX IT IF IT AIN'T BROKEN?

[Yes, I run Slackware!]

Watchdogs of the OpenSource Movement considers the kernel a viable project because... it is growing
10.000 lines a year - !YIKES, soon my 2.66DualCore2 monster won't be able to handle it!

And I say: It's all because of U.

Because of this pressure put on a six-months release cycle - something that only works for them, because it contributed to attract a crowd of novelty-avid followers and tinkerers that are happy re-installing their system every six months. Sh*t, I like to fool around, but I use sandboxes and virtualmachines for that, not my desktop!

C'mon, when you watch the websphere today, it's like every distro release out there has to be on U's pace. That' s crazy. Since when do you hurry respectable old ladies in the stairwell? Debian and Slackware both looks like they are running out of breadth, while knowing they can't compete. Luckily, they achieve stable releases we can work on. KDE 3.5.10 anyone? You can't beat Konqueror wealth of features and file handling compliances in 3.5.10.

I _just_ mistakenly, as root, deleted my full /usr folder. Has anything stopped running? no, Slack is light on RAM. How long did it take me to recover a system that just lost _all_ it's executables?

25 minutes, including the extra tarballs and special Window Manager I compiled from source. (e16)

Did I had to reboot? No. I am still writing to you. :)

Rock Solid Old Dog - that's the way it should be.

Bleeding Edge should be an option, not a competition. But it seems it has become part of linux success, and as such it is now an egg/chicken problem.

So, to people out there that would have made it down here: NEVER assume a newer version number to be better; If your version is working, KEEP IT! And if you do have issues, don't assume: you can only click on "upgrade" with hope, nothing more.

Jean-Philippe - Slackware 12.2.
Celebrate Hannibal Day this year. Take an elephant to lunch.

Thursday, February 12, 2009

On the Inability of this whole system to actually help you in any useful way

Howdy, Nixettes and Nixers!

In my article "Bug Bang II: Revenge of the Devs" I was unfair; boldly, plainly unfair, but you'd have to dig into Fedora/RedHat strategy of dodging the bullet to learn how misplaced one can be when ones submits a bug, sees it discarded, and shamelessly, rudely even, makes a fuss about it.

Doing so, you are hitting the wrong person. I was crawling the fedora quite obscurely organised sphere of "community" websites (Join! Get! Communicate! Wiki! Planet!! - ??) and realised this: They've build their own Community Firewall of volunteer bug-bashers. Who are they? They are not RedHat people, they are volunteers that commit self-sacrifice of their free time in reviewing bugs, tasked by their masters with one duty in their faithful lives: bash them, squash them, write off a maximum of them 'cause so much of them aren't really bugs. You know that, they aren't bugs, they are features. duplicates,... Or temporary shortcomings. Or, mainly, they are Someone Else's Problem. And certainly, you can't waste precious Devs time reviewing them.

And so if for one moment you felt you did your community job of End User by taking the time to register to a website, search for duplicates, submit and document your issue, all because it's not because you can't code that you can't participate, you are wrong.

Users are such a pain in the ass. Why should Devs, the semi-Gods of OpenSource, have to bear with them? They are incompetent, they cry over the littlest of glitches all the time (469045: No DVD Drive! 251080: Laptop doesn't switch back on!). EndUsers can't compile code anyway, let alone commit a patch: Pussies!

The fundamental concept of SEP (Someone Else's Problem) is one that allows our SemiGods to focus on the all-important matters of providing us with a new version of their almighty, sacred Code, again and again in their imaginary world of up-to-date-bleeding-edge novelties, as soon as possible, so that they don't feel left behind, outdated, discarded (and disrupted in their Sacred Workflow); and to do that, you have to be protected from them, and also you have to distract them by coercing these fucking users into upgrading their whole operating system every six months (for as utterly crazy as it sounds), and download gigs of all-important updates in the meantime. I can actually understand that, from the human side: Who, seriously, likes to have its failures documented, published, and be publicly requested to amend and fix them? Nobody, of course.

One thing may explain the other anyway: Obviously, why focus on a bug in code that has an official life expectancy of barely six months? (and hurting someones' valuable self in the process?) The first to answer "So that the next release is bug-free", please go back to whatever FairyTale world you happen to live in: I upgrade my desktop, webcam ceases to work; I upgrade the laptop, Compiz crashes the system twice a day.

And when will NetworkManager actually remember my fucking password? When will Gnome restore autologin? When will they really come around a real one-click solution to mp3/DVD reading that doesn't involve buying stuff from the Internet or discarding multiple hypothetical patents warnings? You can hardly do that in one click. Will my Syntek webcam die when the kernel starts to include drivers for it, while it works perfectly if I compile the module myself, like it happened with my Logitech STX? When will Linux systems start to use the same amount of battery power as XP does?

When will they start committing and releasing code with an actual life expectancy of more that a few moths?

When will they start pushing code up & downstream when it is actually ready for production?