The cluster

[Idolrevolver]

Surely you're not so full of hatred for Microsoft that you would foist Linux on a person, with no consideration for circumstance.

Hatred is not required. GNU/Linux is nowhere near as difficult to install and use as you imply. With Ubuntu especially, installation is as simple as boot to disk image and click the buttons. The only learning is where the menu is, provided you use the same or equivalent software as you are used to.

[Felblood]

When the user is ready, he will come to Linux, and it just needs to be there, waiting for him. You don't have to take it to him.

A person's first Linux experience should occur under optimal circumstances. Indeed, it needs to, if the switch is going to stick. We're not looking for sword-point converts here; we just want to show people how Linux can make their lives better. I'm not saying the switch isn't worth it, but I am saying it isn't always a good time to make it.

The thing that most drives people away from Linux isn't Linux itself, it's the people who use it. The Linux community can be very (even overly) welcoming, right up until you have a problem and need help, at which time they can get downright nasty in their overzealous defense of their sacred cow. (Windows users tend to adopt more of a "We're all stuck in this mess together, so let's work together" sort of approach, and the sudden shift can be very jarring for new people.)

I would council against taking technology advice from a zealot. However, not everything a zealot believes is automatically false, and it would be unfair to let the more fervent members of any group be it's sole representatives.

When a person finds himself asking, "Should I just switch to Linux?" he's probably ready. Just make sure you back up your data before you make any major changes, Doctor100.

The key with a Linux system is knowing what not to do, so you feel free to play in the remaining space; if you don't have the confidence to tinker, there's really no point. It's a bit like programming a new VCR, really; the very hardest part, is screwing up the courage to just push some buttons, on an unfamiliar interface. I'm not saying everything is going to be roses and puppy dogs after that, but if you can do that, then you're doing better than most people.

You're a smart guy, and you wouldn't be asking unless you had some time and interest to invest in this project. So sure, give it a whirl. Let us know how it works out for you.



Back on topic:

The cluster is definitely custom hardware, now. Assuming even marginal sanity on the part of the developer, is there anything left we can count on?

[Turing Manchine]

I just thought I'd point out that Ellen's remark about the cluster being less powerful than the sum of its parts doesn't make that much sense. It always takes some overhead to get computers to work together on a problem.

[Tropylium]

I just thought I'd point out that Ellen's remark about the cluster being less powerful than the sum of its parts doesn't make that much sense. It always takes some overhead to get computers to work together on a problem.

What sort of left me wondering about that is, working out the cluster's computing power seem'd to be the first thing she check'd? Doesn't that take all sorts of tests?

…Anyway, Jamie's grin in the last panel of #20 is priceless.

[doctor100]

Here's my concern: as I said, I haven't used command prompts since I was a child. Now, while I am willing to recreate the lack of caution that a child has, in order to know a new system, and I am even willing to learn a new system that is esoteric; I am concerned about the time period it takes to learn.

and I don't see the point in doing something that will frankly limit my capabilities, for the potential trade off of gaining capabilities, including what is probably a very large devotion of time, if in fact, I gain no capabilities. Tech is not my field. I have never had a C++ programing class, I have never had a class in any similar field, the closest I come is MS excel, or a typing class, take your pick.

As for damage to existing systems, as I implied I've been using a variety or different computers, I have learned not to store anything on a machine, everything in in the cloud, hosted by google. My default word proccessing is google because I can use it anywhere. Not really worried about messing up a machine, worried about not being able to use a machine (I know ubuntu is safe but . .) I am worried about taking a step towards something I know nothing about and not making any progress in the field. If I use linux, then I want to be good at it, to be able to create not just use. Unfortanatly I do not know the time period that would be required learning, nor the wait on returns.

any clues?

[doctor100]

Alright, so naturally, I have been looking at the world wide web to sorta help me with this decision. My big problem is . . .carpel tunnel. I cannot use a text entry system[*], which it seems I must if I want to get great additional use out of the system, right?

[*not without making my disability worse]

Now, I can speak, and I can use handwriting, what this has led me to is a shorthand reconition: think something like http://en.wikipedia.org/wiki/Graffiti_(Palm_OS) except perhaps a bit more like http://en.wikipedia.org/wiki/Gregg_shorthand

Now, the question remains; lets say I devote the time to learn enough to use the command system; seeing as I doubt the program exist, tying a shorthand, writing pad, and command prompt all together; could I, within a years time of learning, be able to program such a program myself?

Just assume I'm you regarding my capability with a learning curve.

[Felblood]

Oh, carpal tunnel.

The other reason I don't really do much Linux stuff (or even write code at all really. It's hard for the ideas to flow when you're fighting your fingers to type them in.)


The trouble with getting accessibility features from an open source project is that the only people who need these features are highly unlikely to implement them.

Source Forge is littered with half-completed voice and handwriting recognition plug-ins. Apathy, disinterest and disorder are what kills open source projects, and once they die, it can be near impossible to revive them or retrieve the effort that was wasted in them.

In a commercial project, there is an incentive and a leadership structure that drive the team to develop software that is of no value to themselves, but can be sold to other users. Charity, sadly, typically only lasts long enough to fork over a couple of quarters, not nearly long enough to see a major project through hard times. Human nature will get us all, sooner or later.

[doctor100]

I believe that RonInnomBab is saying the for carpel tunnel /he recommends; 800mg ibuprofen and 180 codeine mg

side effects include: debt, max ehrmann, depression, credit counseling, Swollen glands, bad taste,
? Liger sale

Ron: I'ma Bab[yl;

[Alex Starkiller]

He also wants to know how to make a diaper cake.

[doctor100]

the stork brings it.