Really? Cause, your download page warns that it's a beta product and should not be used in production.
We do that as a preventative measure for people that don't get support through us. We don't want anybody to assume that the file system is ready for a highly-available cluster without talking to us first.
That word, 'beta', I do not think it means what you think it means.
Just start with that -- a easy-to-use (whatever that means in the parallel programming case) and full-featured debugging tool. I think a lot will follow from that, especially if one can get to the bottom of what 'easy-to-use' and 'full-featured' means in the parallel programming case. And frankly, I believe it's Intel's and Microsoft's responsibility to step up on this.
The ability to buy freedom for +$0-$100 more than the alternative, and invest in potentially a positive feedback loop of more and more vendors attempting to make Dell buy their components, thereby improving linux compatibility across the field?
Sure. If someone had gone through all the work of setting up Ubuntu for me, I'd probably be a happy user right now. Unfortunately, I didn't have that luxury.
And before you say, "but if people had to install Windows...": well, they don't.
Why is it that 'installing' the software gets so much coverage? Most installers are designed to be flexible enough to cover pretty much any custom setup in a one-shot pass, and as a result becomes difficult for new users. And you do it once. Once that's behind you, there's still a battleground for application quality and user experience for the other 700 or so days of the life of that system you spent maybe up to a week installing the software on.
I think Linspire has at least this part right, as they make an effort to sell the consumer O/S preinstalled on systems. This skips this whole one-time morass and moves on to the jungle of the quality and variety of apps and the day-to-day end-user experience. I'd be happy if reviews never again mentioned the initial install of an O/S because 1) Comparing a pre-installed Windows system vs. the installer on Linux systems on the basis of ease of installation, Linux will always lose for the general consumer, 2) You only install it once.
I liken debian to my Honda Civic, or maybe even to public transportation
with a yearly pass. Get in, show your pass/turn the ignition, and maybe
every year and a half, buy a new pass or drop it off for maintenance for a
couple days. Not as attractive as this year's model, but reliable to the
point where you rarely think about it.
It takes *a lot* of self-discipline to write maintainable/readable Perl, so not surprisingly lots of Perl code is junk.
It takes a lot of self-discipline -- a lot -- to write readable, well-structured English -- even more so than Perl, because it doesn't even have to pass a syntax check -- so not surprisingly, lots of English is junk. Perl purports to be accessible to beginners and experts, and to make easy things easy and difficult things possible, and as a result, it's more feasible to turn a poor design or no design at all into working code (which then serves as a working proof-of-concept for the next redesign).
Mod me tangential, please -- but I had an unusual experience with a japanese-style acupuncturist who was treating me for something else, and inserted a needle at the bottom of my neck. Immediately, my lung capacity increased by something like 20%, and a couple seconds later she mentioned, what appeared to be coincidentally, 'That's an asthma point'.
This happened 3 weeks ago and I'm still feeling the increased lung capacity or chest tightness decrease or whatever. About a year ago, when I started treatment for the separate condition, she had mentioned to me (again, incidentally) that she had successfully treated another woman for asthma who was able to completely go off medication. (I'm still taking the asthma meds, but am considering going off them soon).
Each session was all of $70, and a typical run is 6-8 sessions (per her). In my case, as soon as she needled that spot, it was an immediate effect. It's such a strange feeling now to inhale up to the point where I would have to stop before, and then continue inhaling past that point -- particularly during the summer, when I feel like being more active but my asthma has traditionally been more problematic. It's just not an issue anymore.
Frankly, I don't believe sticking a couple needles into your neck can help you breathe better. Which is why I keep taking deep breaths and being surprised when I feel my chest muscles stretch under a lung expansion I haven't felt in years.
As a researcher in trying to integrate knowledge I find this more and more dissapointing.
Disappointment means your expectations are not being met. That's happening often enough nowadays that we should be moving on to aggravaion, infuriation, and finally, hopefully, action ? I guess the researchers gotta climb out of their ivory tower or at least start throwing bricks out the window sometime, preferably sooner rather than later.
cplay is pretty cool for a music player. Browse dirs, create a playlist, and play/pause/stop/ff/rew , prev/next/first/last all your tracks from a curses ui. It's a 1Kloc python script and uses a couple auxiliary programs. Who needs a 10Mb GUI to play a few tunes?
I've been writing perl for 15 years now, but what attracted me to it originally was the perl 4 documentation. That's my best example of friendly, nonpedantic documentation. In fact, I tell everybody that what attracted me to the language was the way design decisions and suggested usage was clearly expressed in the documentation. It made me think, if the *documentation* is this clearly thought out, software that it represents will be of comparable quality. It's sort of like seeing someone in the parking lot step up and help an old lady carry her groceries to her car while everybody else just walks by. You gain confidence that there's a certain level of quality/civility you can count on even if you're not sure about external appearances.
In perl's case, it gets across that its first priority is to be useful and honest, but not perfect or that its way is the right way to do things (e.g., 'you don't need stored procedures in a database, write your business logic in your code' vs. 'we don't have stored procedures yet; if you really need them, mysql may not be for you').
Since then, perl5 documentation has had contributions from multiple writers, so the writing styles can be a bit uneven. But they're still pretty good. Another important factor contributing to quality is that the module guidelines state that the documentation authoritatively specifies the module API and public/protected variable, etc distinction, not compiler- or language-enforced access controls. That kind of attitude encourages the documentation to have a certain level of clarity at the beginning.
So read the perl4 documentation. It's a good example. I personally would start by looking at man pages/docs that I've read, said 'oh man, this needs so much more information', and put the info in there. It's easy to justify the time on it when you have a personal stake because you're using the tools themselves; just jot down notes in complete sentences about actual usage, gotchas, etc, as you use the tool, and when you have a few free minutes, drop a note to the maintainer with a doc patch.
The shielding can reduce the coupling of radio waves, electromagnetic fields and electrostatic fields, though not static or low-frequency magnetic fields. (A conductive enclosure used to block electrostatic fields is also known as a Faraday cage.) The amount of reduction depends very much upon the material used, its thickness, and the frequency of the fields of interest.
Unless the safe was made of mu metal, I suspect the kettle could have demagnetized the tape if it was producing a low-frequency or static magnetic field.
That's what the rest of the world thinks when they hear "free".
I thought English was one of the few (?) languages that used 'free' to mean
'gratis' as well as 'libre', and that the 'rest of the world'
had language support [sic] to distinguish the two concepts.
2) Never look at the products at eye level, they are the most expensive and worst value.
If that were the case, shouldn't candy, cookies, ice cream, and action figures be spread out over the entire store on shelves about 2-3 feet from the ground?
I always thought of perl more as a multiheaded dog that will run you down, jump on your chest, and simultaneously sniff and lick you with every head while barking about how happy it is to see you.
In other words, friendly... but maybe a bit too friendly.
I don't get it. When you have that many choices, can't you flip the problem around by visualizing a few choices of how you would like your house to look, then picking the closest matching carpet/style? That's what I do when considering a laptop purchase.
Oh, and re: making a decision; I'd start with Consumer Reports for the 'functional' parts (durability, stain resistance, etc) and maybe find some home visualization software, if such exists, and try out the various carpet types. Or, like I said, just close your eyes and imagine the possibilities first. Or go to a real carpet store and ask for suggestions on picking out a style. I figure people who work at dedicated carpet places would have some ideas.
Running Linux, this means you can cache all of/usr/bin and much of/lib and/usr/lib in RAM before you fire up your desktop. Then all your apps start up straight out of RAM, and pretty much all other disk access as well (see my similar comment).
The wet dream of inexpensive, high-density RAM is now a reality. But none of us suspected that the limiting factor in improving desktop performance would be, of all things, finding an inexpensive desktop motherboard that takes 8x DIMMs.
Slashdot Mirror
We do that as a preventative measure for people that don't get support through us. We don't want anybody to assume that the file system is ready for a highly-available cluster without talking to us first.
That word, 'beta', I do not think it means what you think it means.
KDE bug 140983 .
Just start with that -- a easy-to-use (whatever that means in the parallel programming case) and full-featured debugging tool. I think a lot will follow from that, especially if one can get to the bottom of what 'easy-to-use' and 'full-featured' means in the parallel programming case. And frankly, I believe it's Intel's and Microsoft's responsibility to step up on this.
Or an iGasm. That would be news.
The ability to buy freedom for +$0-$100 more than the alternative, and invest in potentially a positive feedback loop of more and more vendors attempting to make Dell buy their components, thereby improving linux compatibility across the field?
And before you say, "but if people had to install Windows ...": well, they don't.
Why is it that 'installing' the software gets so much coverage? Most installers are designed to be flexible enough to cover pretty much any custom setup in a one-shot pass, and as a result becomes difficult for new users. And you do it once. Once that's behind you, there's still a battleground for application quality and user experience for the other 700 or so days of the life of that system you spent maybe up to a week installing the software on.
I think Linspire has at least this part right, as they make an effort to sell the consumer O/S preinstalled on systems. This skips this whole one-time morass and moves on to the jungle of the quality and variety of apps and the day-to-day end-user experience. I'd be happy if reviews never again mentioned the initial install of an O/S because 1) Comparing a pre-installed Windows system vs. the installer on Linux systems on the basis of ease of installation, Linux will always lose for the general consumer, 2) You only install it once.
Radiation was a big problem even in olden times -- I wouldn't be surprised if lawsuits start popping up about this nowadays as well.
I for one, am pleased to welcome our frickin' superconducting laser shark overlords.
I liken debian to my Honda Civic, or maybe even to public transportation with a yearly pass. Get in, show your pass/turn the ignition, and maybe every year and a half, buy a new pass or drop it off for maintenance for a couple days. Not as attractive as this year's model, but reliable to the point where you rarely think about it.
Maybe they should, maybe they shouldn't -- but they should all at least be on equal footing in this regard, right?
It takes a lot of self-discipline -- a lot -- to write readable, well-structured English -- even more so than Perl, because it doesn't even have to pass a syntax check -- so not surprisingly, lots of English is junk. Perl purports to be accessible to beginners and experts, and to make easy things easy and difficult things possible, and as a result, it's more feasible to turn a poor design or no design at all into working code (which then serves as a working proof-of-concept for the next redesign).
Then again, maybe this isn't really that unexpected?
P.S. Perl::Critic attempts to alleviate these sorts of problems.
Mod me tangential, please -- but I had an unusual experience with a japanese-style acupuncturist who was treating me for something else, and inserted a needle at the bottom of my neck. Immediately, my lung capacity increased by something like 20%, and a couple seconds later she mentioned, what appeared to be coincidentally, 'That's an asthma point'.
This happened 3 weeks ago and I'm still feeling the increased lung capacity or chest tightness decrease or whatever. About a year ago, when I started treatment for the separate condition, she had mentioned to me (again, incidentally) that she had successfully treated another woman for asthma who was able to completely go off medication. (I'm still taking the asthma meds, but am considering going off them soon).
Each session was all of $70, and a typical run is 6-8 sessions (per her). In my case, as soon as she needled that spot, it was an immediate effect. It's such a strange feeling now to inhale up to the point where I would have to stop before, and then continue inhaling past that point -- particularly during the summer, when I feel like being more active but my asthma has traditionally been more problematic. It's just not an issue anymore.
Frankly, I don't believe sticking a couple needles into your neck can help you breathe better. Which is why I keep taking deep breaths and being surprised when I feel my chest muscles stretch under a lung expansion I haven't felt in years.
Disappointment means your expectations are not being met. That's happening often enough nowadays that we should be moving on to aggravaion, infuriation, and finally, hopefully, action ? I guess the researchers gotta climb out of their ivory tower or at least start throwing bricks out the window sometime, preferably sooner rather than later.
If it was good enough for this guy, it should be good enough for you.
cplay is pretty cool for a music player. Browse dirs, create a playlist, and play/pause/stop/ff/rew , prev/next/first/last all your tracks from a curses ui. It's a 1Kloc python script and uses a couple auxiliary programs. Who needs a 10Mb GUI to play a few tunes?
In perl's case, it gets across that its first priority is to be useful and honest, but not perfect or that its way is the right way to do things (e.g., 'you don't need stored procedures in a database, write your business logic in your code' vs. 'we don't have stored procedures yet; if you really need them, mysql may not be for you').
Since then, perl5 documentation has had contributions from multiple writers, so the writing styles can be a bit uneven. But they're still pretty good. Another important factor contributing to quality is that the module guidelines state that the documentation authoritatively specifies the module API and public/protected variable, etc distinction, not compiler- or language-enforced access controls. That kind of attitude encourages the documentation to have a certain level of clarity at the beginning.
So read the perl4 documentation. It's a good example. I personally would start by looking at man pages/docs that I've read, said 'oh man, this needs so much more information', and put the info in there. It's easy to justify the time on it when you have a personal stake because you're using the tools themselves; just jot down notes in complete sentences about actual usage, gotchas, etc, as you use the tool, and when you have a few free minutes, drop a note to the maintainer with a doc patch.
The shielding can reduce the coupling of radio waves, electromagnetic fields and electrostatic fields, though not static or low-frequency magnetic fields. (A conductive enclosure used to block electrostatic fields is also known as a Faraday cage.) The amount of reduction depends very much upon the material used, its thickness, and the frequency of the fields of interest.
Unless the safe was made of mu metal, I suspect the kettle could have demagnetized the tape if it was producing a low-frequency or static magnetic field.
I thought English was one of the few (?) languages that used 'free' to mean 'gratis' as well as 'libre', and that the 'rest of the world' had language support [sic] to distinguish the two concepts.
2) Never look at the products at eye level, they are the most expensive and worst value.
If that were the case, shouldn't candy, cookies, ice cream, and action figures be spread out over the entire store on shelves about 2-3 feet from the ground?
In other words, friendly ... but maybe a bit too friendly.
When Windows gets kioslaves, I'll believe in seamlessness. If Vista has an equivalent, I'm willing to give it a shot.
Oh, and re: making a decision; I'd start with Consumer Reports for the 'functional' parts (durability, stain resistance, etc) and maybe find some home visualization software, if such exists, and try out the various carpet types. Or, like I said, just close your eyes and imagine the possibilities first. Or go to a real carpet store and ask for suggestions on picking out a style. I figure people who work at dedicated carpet places would have some ideas.
- Put in 4x1GB sticks for about $300.
Running Linux, this means you can cache all ofThe wet dream of inexpensive, high-density RAM is now a reality. But none of us suspected that the limiting factor in improving desktop performance would be, of all things, finding an inexpensive desktop motherboard that takes 8x DIMMs.