Where this can be damned useful though is if a.com domain has a.xxx twin then you can be/relatively/ sure that you can possibly block both (I know, I know, there are some cases where that won't be the case).
Should be interesting,.xxx domains getting listed by people who want to blacklist various.com domains:-D
Now I can get my [fake mail order] University Degree/and/ real [bacterial] culture diversity all on the same certificate.... just like if I had gone to Univeristy and dorm-hopped, or eaten cafeteria food.
What on earth? It's not like the K* apps are the only ones on the radar that are any good. Some of us can work just fine without.
K3b... learning mkisofs and cdrecord isn't that hard, takes up less resources, that's for sure. amarok... xmms is a guzzler too but there are others like ogg321 for command line replacement kopete... GAIM konq... Firefox kate/quanta...vim or gvim
Personally when it comes to productivity, not using K*apps isn't a limiting factor. All the above running on Fluxbox is just dandy thanks. If I want eye-candy perhaps I'll fire up XFCE instead.
I have to entirely agree with your sentiment. Pushing past the stage of "It works for me" is usually what separates the wheat from the chaff.
I know pushing a few of my products to have a commercial face has required quite a few thousand hours of repetitive, boring and rather tedious work. There's a degree of finish associated with professional products that is outside of the actual software itself in most of the cases (boxart, manuals, websites, support infrastructure, pricing... ugh, the list goes on).
This would apply if all the people in the world paid for the research to get the patent. However since the research was paid by Australians, that would only apply to Australians:-)
"""
Dispose of cells/packs as follows: a. Discharge: with the cell/pack in a safe area, connect a moderate resistance across the terminals until the cell/pack is discharged. CAUTION: cell/pack may be hot! b. Discard: - LiPo: puncture plastic envelope, immerse in salt water for several hours, place in regular tras """
specifically """ Disposal of cells or packs. Discharge all cells individually to recommended cut-off voltage. Caution!! Cells may be warm or hot as usual during this discharge process. After cooling, puncture small hole in cells and immerse in salt water for 2 hours. Apply tape over one terminal and dispose of in trash. """
The iPod uses lithium poly batteries, they're slim, they're powerful and they pack a punch when you rupture them.
With model aircraft, we use them a lot for our electric motors however they carry with them a lot of cautions. If you should happen to rupture or over charge them it's time to STAND CLEAR.
Typically a lipo will puff up for a bit then have a fairly impressive flame out (as the lithium starts burning). I'd personally be worried about the guy if he inhaled too much of the fumes, it's fairly toxic.
Oh, he probably ruptured the battery with the screwdriver. Normally if we have a "dud" cell, we put the cells into a bucket of salt water and then puncture the cells (UNDER WATER), the cells will bubble quite a bit and eventually after a few hours settle down.
A shame you're posting as AC, but I suspect you had to in this case.
Interestingly, this is why I put my source out under the BSD licence, because I know that I quite often need (and use) equivilantly licenced source, two such examples are Henry Spencers' regex lib and the SQLite engine.... do onto others what you expect others to do onto you.
That's very correct. The reason being is due to wind-resistance/drag.
Essentially in order to double your speed you have to square your engine power (general rule of thumb!), subsequently you can use almost twice as much fuel trying to do 110km/hr as if you were doing 90km/hr.
I forgot to note that the "noise" that you're suffering is from the grooving they put into the concrete road. Without this grooving people would be crashing everywhere when it starts raining from aquaplaning (even the smoothest asphalt road will not be as slippery as a wet smooth concrete one).
Concrete roads are far more resiliant to wear than asphalt/tar roads, this means (generally) less repair work. This is a major factor when you're dealing with a massive arterial system.
Overall concrete roads and asphalt tend to work out the same in terms of costs (over a period of years), concrete being more expensive to lay but lower repairs and vice-versa for asphalt.
All I can say then is why don't you come and join the cc-talk mailing list and see how the actual people who are being offered this feel. Would be good to have some constructive counter-opinons and dialog.
"I'm not asking that you allow yourself to be burnt, but I think you're actually taking advantage of down and out developers with your current approach, whether that's your intention or not."
A few points you should be aware of:
- They choose if they want to be involved
- They only code on OpenSource software (I suppose then the whole community is taking advantage of them)
- It allows them to avoid having to do other work that they might not have been wanting to (cleaning up roadside litter vs programming?)
- They get credited for doing the work and subsequently don't get harassed by the departments
*hands over an iceblock* here, hold this - you need to cool down.
I actually do 99% of my own work, over a dozen Opensource projects and one commercial project, which incidently funds donations to other Opensource projects (not just my own).
I am not interested in slave-labour, I much rather have one good worker/contractor I can rely on. Slave labour as such gains nothing for anyone.
My original point was (which seems to have been misconstrued) that it's difficult to find people who have good coding standards, who aren't trying to use all sorts of crazy code tricks to show-off, who actually -can- work within set specifications.
There's a lot of people out there who read a "Learn C in 24 hours" book and suddenly decide that they can put that on their CV "C programmer" or who have done some perusing of HTML and all of a sudden are "WWW developers". The problem at hand isn't that these people are starting out, well all have to start somewhere, it's the disparity between their skills and their perceived value (per hour), think back to the dot.com era.
So, back to the original concept of community-code, I think it's a great idea still. If there are skilled coders out there, then they get to code "for the dole" without having to be pushed into a road-side clean up. For those less-skilled coders, this gives them an opportunity to get some experience and feedback. For people like myself, it gives us a chance to interact with more local coders (we don't all live in the big cities) and possibly strike up some future collaborations.
What a waste of 5 minutes of my life and a few hundered K of downloads:-\
Turns out this was nothing more than an extended opinon piece (yes, yes, I know that's perfectly fine) but I was looking for something with some hard-core comparisons, especially since they started out saying "we'll just compare the desktop scenario to keep matters simpler" --- *click to next page* Aw what!? nothing!
Sounds like someone was just after some slashdot publicity.
Slashdot Mirror
Not too sure I'd trust a company selling $1500 cables with a l33+ AOL email address like:
...especially since they already appear to have a web site (audio-magic.com).
Aud1omagic@aol.com
I think someone's having a huge laugh as they drive to the bank in their .
Win.tel :-)
Wonder who's going to buy me out.
That the entry form is in MS Office DOC format :-(
Come on guys, how about PDF or plain HTML.
Where this can be damned useful though is if a .com domain has a .xxx twin then you can be /relatively/ sure that you can possibly block both (I know, I know, there are some cases where that won't be the case).
.xxx domains getting listed by people who want to blacklist various .com domains :-D
Should be interesting,
Now I can get my [fake mail order] University Degree /and/ real [bacterial] culture diversity all on the same certificate.... just like if I had gone to Univeristy and dorm-hopped, or eaten cafeteria food.
Dumb question perhaps but... why do you need smooth pixel blending? Wouldn't that simply make it /harder/ to edit the graphics accurately?
Can't believe no one appears to have bought this up, there is a new generation of Li batteries, the LiS battery, coming out.
The LiS chemistry offers up to 3x the energy density of the current LiPoly and an extremely favorable charge rate.
http://www.electronicsweekly.com/Article19790.htm contains some basic information, google for some more.
What on earth? It's not like the K* apps are the only ones on the radar that are any good. Some of us can work just fine without.
K3b... learning mkisofs and cdrecord isn't that hard, takes up less resources, that's for sure.
amarok... xmms is a guzzler too but there are others like ogg321 for command line replacement
kopete... GAIM
konq... Firefox
kate/quanta...vim or gvim
Personally when it comes to productivity, not using K*apps isn't a limiting factor. All the above running on Fluxbox is just dandy thanks. If I want eye-candy perhaps I'll fire up XFCE instead.
K* gives me little more than a slower machine.
I have to entirely agree with your sentiment. Pushing past the stage of "It works for me" is usually what separates the wheat from the chaff.
I know pushing a few of my products to have a commercial face has required quite a few thousand hours of repetitive, boring and rather tedious work. There's a degree of finish associated with professional products that is outside of the actual software itself in most of the cases (boxart, manuals, websites, support infrastructure, pricing... ugh, the list goes on).
Anyone notice that the QinetiQ text on the nose of the harrier looks (poorly) photoshopped on?
This would apply if all the people in the world paid for the research to get the patent. However since the research was paid by Australians, that would only apply to Australians :-)
Also from Kokam - one of the major suppliers of Lipo's for R/C usage
http://www.kokam.com/english/biz/warning.html
"""
Dispose of cells/packs as follows:
a. Discharge: with the cell/pack in a safe area, connect a moderate resistance across the terminals until the cell/pack is discharged. CAUTION: cell/pack may be hot!
b. Discard:
- LiPo: puncture plastic envelope, immerse in salt water for several hours, place in regular tras
"""
Depends on the maker - the salt water is also used to neutralize the lithium compounds.
Refer to: http://www.toddsmodels.com/Lithium/Lithium.htm
specifically
"""
Disposal of cells or packs.
Discharge all cells individually to recommended cut-off voltage.
Caution!! Cells may be warm or hot as usual during this discharge process.
After cooling, puncture small hole in cells and immerse in salt water for 2 hours.
Apply tape over one terminal and dispose of in trash.
"""
Actually, that's the recommended method of disposal by the manufacturers.
The lithium in the batteries are in ionic or bound form typically so it's not immediately like pure lithium in contact with the environment.
http://www.rcmaterial.com/LipoManualEN.htm
See the section on "Disposal Methods"
Note the critical factor of "salt".
The iPod uses lithium poly batteries, they're slim, they're powerful and they pack a punch when you rupture them.
With model aircraft, we use them a lot for our electric motors however they carry with them a lot of cautions. If you should happen to rupture or over charge them it's time to STAND CLEAR.
Typically a lipo will puff up for a bit then have a fairly impressive flame out (as the lithium starts burning). I'd personally be worried about the guy if he inhaled too much of the fumes, it's fairly toxic.
Oh, he probably ruptured the battery with the screwdriver. Normally if we have a "dud" cell, we put the cells into a bucket of salt water and then puncture the cells (UNDER WATER), the cells will bubble quite a bit and eventually after a few hours settle down.
A shame you're posting as AC, but I suspect you had to in this case.
Interestingly, this is why I put my source out under the BSD licence, because I know that I quite often need (and use) equivilantly licenced source, two such examples are Henry Spencers' regex lib and the SQLite engine.... do onto others what you expect others to do onto you.
That's very correct. The reason being is due to wind-resistance/drag.
Essentially in order to double your speed you have to square your engine power (general rule of thumb!), subsequently you can use almost twice as much fuel trying to do 110km/hr as if you were doing 90km/hr.
Amen!
Seriously, this is what happens when you give kids too many toys too easially, they expect more and more.
I forgot to note that the "noise" that you're suffering is from the grooving they put into the concrete road. Without this grooving people would be crashing everywhere when it starts raining from aquaplaning (even the smoothest asphalt road will not be as slippery as a wet smooth concrete one).
Paul.
Concrete roads are far more resiliant to wear than asphalt/tar roads, this means (generally) less repair work. This is a major factor when you're dealing with a massive arterial system.
Overall concrete roads and asphalt tend to work out the same in terms of costs (over a period of years), concrete being more expensive to lay but lower repairs and vice-versa for asphalt.
All I can say then is why don't you come and join the cc-talk mailing list and see how the actual people who are being offered this feel. Would be good to have some constructive counter-opinons and dialog.
"I'm not asking that you allow yourself to be burnt, but I think you're actually taking advantage of down and out developers with your current approach, whether that's your intention or not."
A few points you should be aware of:
- They choose if they want to be involved
- They only code on OpenSource software (I suppose then the whole community is taking advantage of them)
- It allows them to avoid having to do other work that they might not have been wanting to (cleaning up roadside litter vs programming?)
- They get credited for doing the work and subsequently don't get harassed by the departments
Damn, just wasted those gains reading your post!
*hands over an iceblock* here, hold this - you need to cool down.
I actually do 99% of my own work, over a dozen Opensource projects and one commercial project, which incidently funds donations to other Opensource projects (not just my own).
I am not interested in slave-labour, I much rather have one good worker/contractor I can rely on. Slave labour as such gains nothing for anyone.
My original point was (which seems to have been misconstrued) that it's difficult to find people who have good coding standards, who aren't trying to use all sorts of crazy code tricks to show-off, who actually -can- work within set specifications.
There's a lot of people out there who read a "Learn C in 24 hours" book and suddenly decide that they can put that on their CV "C programmer" or who have done some perusing of HTML and all of a sudden are "WWW developers". The problem at hand isn't that these people are starting out, well all have to start somewhere, it's the disparity between their skills and their perceived value (per hour), think back to the dot.com era.
So, back to the original concept of community-code, I think it's a great idea still. If there are skilled coders out there, then they get to code "for the dole" without having to be pushed into a road-side clean up. For those less-skilled coders, this gives them an opportunity to get some experience and feedback. For people like myself, it gives us a chance to interact with more local coders (we don't all live in the big cities) and possibly strike up some future collaborations.
What a waste of 5 minutes of my life and a few hundered K of downloads :-\
Turns out this was nothing more than an extended opinon piece (yes, yes, I know that's perfectly fine) but I was looking for something with some hard-core comparisons, especially since they started out saying "we'll just compare the desktop scenario to keep matters simpler" --- *click to next page* Aw what!? nothing!
Sounds like someone was just after some slashdot publicity.