Sounds like your boss has a business degree of some nature.
1) Warez are not OSS, OSS is not Warez. The fundamental difference is the ability to fix things. 2) If you reasonably depend on software to work, no matter what the cost of that software, you will make it work (or get a friend to make it work). This especially applies to those without disposable income (unlike your boss) 3) a) When you have the ability to fix things (alons with everyone else), the 'cost' of the program becomes the collective effort of those involved in development (active developers, library developers, debuggers, beta testers and users). Averaged out over the users, this becomes a vested interest. As such, when an OSS program that fits a specific need doesn't work, the user is very likely to complain to the developers, who are very likely to fix the bug (bug-fix speed dependant on the specific development model). The end result for vested users is that the mindset becomes "why doesn't our program work?" 4) For users of new OSS programs, it isn't an issue yet. The user must like and need the program as it stands, or its potential, to become involved.
Still, if you have to pay $X00 for a program, and there's an OSS program that does much the same thing, you'll do your damndest to get it working; that OSS program could save you $X00, even if you end up paying it in effort.
If you're using a brush, your paint job will look positively/awful/.
I'd be more worried, however, that when it comes to the buffing stage, the little bumpies in the paint job suddenly become bullet - and thus buffer - proof.
The problem in the US with corn is that it's not really good for anything. It's really low in nutrition as food, and not high enough in sugar to be an efficient ethanol producer (with the sunlight-to-energy conversion yields you get off corn, you might as well solar-panel the countryside).
Yet, there's almost government enforcement for growing the stuff.
That's assuming corn as the only means of obtaining alcohol.
Jerusalem artichokes, for example, get 2-3 times the potential ethanol yield per acre per year as corn, at the small cost of needing a small amount of malt to break down the starches.
Getting ethanol from cellulose would be even better (for example, using hemp or fast-growing trees), ranging 40-50 times the yield of corn.
The research is being done now. I'll call you in a year or so when production starts.
Still, it might not be a bad idea to have flash journalling; have the controller record a disk-to-disk write and return immediately, intelligently handle disk reads, even if the data hasn't been relocated yet, etc. The flash chip just stores a list of actions (like in a journalled FS) and the controller performs them. They can be suitably small (1 block) so as to keep state granularity high.
No, seriously. Sure, lots of filesystems journal, but how many can journal with separated control? In a normal journalled fs, the journal is stored on the same media as the disk - and thus suceptable to the same corruption.
It's like the issues that put journalling in place originally; sure, some data can fail and we're ok, but if the filesystem structures fail, everything is effectively lost.
Please tell me that stink is sarcasm. Cos I don't think I could take Dvorak being compared to a real journalist - even if he was respectable, he's a columnist (writes about his own mishandled opinions), not a journalist (writes the facts).
The raw DVDs, one day, won't be enough. One day, we'll have large enough harddrives to think nothing of dumping uncompressed video to disk, and leaving it around, 'just in case' (TM)
Hacking a site dedicated to exploration of space in order to protest a war they have no interest in or concerns over (when was the last time you saw NASA troops deployed anywhere?)
I suppose it was an easy target. That doesn't make it right, clever, effective, or help anyone become sympathetic. It, instead, gives the impression of a bunch of chilean script kiddies who found an exploit and were using it just as the news releases about lebanon came out.
Well, not exactly. I got a lot of use/fun/work out of my Winux box. I wanted a Mac Mini as a toy to make a MacWinux box, but considering their marketing, I decided my $600 would be better spent on a new mobo/proc (SSE3-supporting, of course) another half-gig of RAM, and a copy of OS-X.
Now, I have my MacWinux box (as well as all the fun I had getting everyone to play together) and no mac to speak of.
So I like the OS. Doesn't mean I have to 1) like the company or 2) use their hardware.
Slashdot Mirror
Meanwhile, Argentina's population are absolutely nuts over linux. I was there about a year ago, and you can see the visage of tux everyehwer.
Um. You ever work with paint?
PEG can be diluted with a quickly-evaporating solvent, thus inhibiting the properties of the finished compound.
Meanwhile, the aperture doen't have to be blocking or small; a simple venturi nozzle should do the trick.
Lastly, if you RTFA, it is sprayed on.
Sounds like your boss has a business degree of some nature.
1) Warez are not OSS, OSS is not Warez. The fundamental difference is the ability to fix things.
2) If you reasonably depend on software to work, no matter what the cost of that software, you will make it work (or get a friend to make it work). This especially applies to those without disposable income (unlike your boss)
3) a) When you have the ability to fix things (alons with everyone else), the 'cost' of the program becomes the collective effort of those involved in development (active developers, library developers, debuggers, beta testers and users). Averaged out over the users, this becomes a vested interest. As such, when an OSS program that fits a specific need doesn't work, the user is very likely to complain to the developers, who are very likely to fix the bug (bug-fix speed dependant on the specific development model). The end result for vested users is that the mindset becomes "why doesn't our program work?"
4) For users of new OSS programs, it isn't an issue yet. The user must like and need the program as it stands, or its potential, to become involved.
Still, if you have to pay $X00 for a program, and there's an OSS program that does much the same thing, you'll do your damndest to get it working; that OSS program could save you $X00, even if you end up paying it in effort.
Just for accuracy, pirated windows from Xerox.
*blinks*
/awful/.
If you're using a brush, your paint job will look positively
I'd be more worried, however, that when it comes to the buffing stage, the little bumpies in the paint job suddenly become bullet - and thus buffer - proof.
*blink*
Coolant + superfine sand = bullet resistant.
nice.
Amusingly enough, it's been termed like that before.
The problem in the US with corn is that it's not really good for anything. It's really low in nutrition as food, and not high enough in sugar to be an efficient ethanol producer (with the sunlight-to-energy conversion yields you get off corn, you might as well solar-panel the countryside).
Yet, there's almost government enforcement for growing the stuff.
Just boggles my fricken mind.
That's assuming corn as the only means of obtaining alcohol.
Jerusalem artichokes, for example, get 2-3 times the potential ethanol yield per acre per year as corn, at the small cost of needing a small amount of malt to break down the starches.
Getting ethanol from cellulose would be even better (for example, using hemp or fast-growing trees), ranging 40-50 times the yield of corn.
The research is being done now. I'll call you in a year or so when production starts.
Still, it might not be a bad idea to have flash journalling; have the controller record a disk-to-disk write and return immediately, intelligently handle disk reads, even if the data hasn't been relocated yet, etc. The flash chip just stores a list of actions (like in a journalled FS) and the controller performs them. They can be suitably small (1 block) so as to keep state granularity high.
No, seriously. Sure, lots of filesystems journal, but how many can journal with separated control? In a normal journalled fs, the journal is stored on the same media as the disk - and thus suceptable to the same corruption.
It's like the issues that put journalling in place originally; sure, some data can fail and we're ok, but if the filesystem structures fail, everything is effectively lost.
Meanwhile, what's good ol' LaPorte doing nowadays?
I dunno. I think Sessler and Webb do a damn good job on video games.
No, I'm afraid I'm going to have to ask you which flavor rock you smoke.
That's right, I pulled the crack card. Yeeah. Wuchuh goon do'boudit?
Please tell me that stink is sarcasm. Cos I don't think I could take Dvorak being compared to a real journalist - even if he was respectable, he's a columnist (writes about his own mishandled opinions), not a journalist (writes the facts).
Still, I'd take the job. I write good tech.
Two words telling where it's a good idea to get a full-screen window: Tabbed browsing.
The raw DVDs, one day, won't be enough. One day, we'll have large enough harddrives to think nothing of dumping uncompressed video to disk, and leaving it around, 'just in case' (TM)
Still, I don't get it.
Hacking a site dedicated to exploration of space in order to protest a war they have no interest in or concerns over (when was the last time you saw NASA troops deployed anywhere?)
I suppose it was an easy target. That doesn't make it right, clever, effective, or help anyone become sympathetic. It, instead, gives the impression of a bunch of chilean script kiddies who found an exploit and were using it just as the news releases about lebanon came out.
Heh. Hell, unless it's core stuff (Qt, for example), I don't see the point in not staticing a lib in.
Query: what percentage of linux distributions use a GNU userland?
The PSU... it's weird. They added this four-pin connector for some motherborads that looks like the main connected.
Oh, so what about that. Five words: defocused artificial large scale understanding.
Not so much 'back to'.
Consider that Newton, Beethoven, et al were the high end of the distribution.
That means that the average human around then was more on the order of Forrest Gump.
I'm sorry. Why do I deserve racism?
I feh on your condemnation of mad science. Now, feel my death ray!
Well, not exactly. I got a lot of use/fun/work out of my Winux box. I wanted a Mac Mini as a toy to make a MacWinux box, but considering their marketing, I decided my $600 would be better spent on a new mobo/proc (SSE3-supporting, of course) another half-gig of RAM, and a copy of OS-X.
Now, I have my MacWinux box (as well as all the fun I had getting everyone to play together) and no mac to speak of.
So I like the OS. Doesn't mean I have to 1) like the company or 2) use their hardware.