Inkjet is vastly inferior to laser in every measure except cost/page.
For their larger version, it is slow. Our new full colour continuous feed laser (not sheet feed, we have a cutter and merger to create the sheets) does over 1000 pages per minute. If your going to go into commercial bureau-style printing, inkjet will never give you the quality you need to blow customers socks off.
A6 is about as big as your hand...double the length to get the A4 length means ~75 pages per minute - nothing to write home about. We have new full colour inkjets here that print thousands of feet per minute - then again their about 12 metres long, so not really for your SOHO market.
according to Novell and SCO, SCO has the licence to develop and sub-license development of Unix V ( I paraphrase from Bruce Perens comments) - so isn't this what M$ bought - a sub-license to develop Unix V ? They didn't buy a licence for Linux as far as I am aware (which isn't a lot)
I know I have buckleys of a reply - I am comment 1108 -(
Re:Beware of overusing patterns.
on
Design Patterns
·
· Score: 1
Christopher Alexander et al (who wrote A Pattern Language, which inspired the GoF to write Design Patterns), stated that one could create a design by 'stringing' patterns together, but that that the result would be 'loose' and unsatisfying. The GoF themselves state that sequentially applying patterns is probably inappropriate as well. Alexander then states that designs that feature overlying and complementing patterns in the same space result in 'a profound effect'. The GoF agree with this too. However, it is implicit that inappropriate overlying or coupling will result in somethind 'profoundly bad'.
OTOH, one of the original authors of 'A Pattern Language' was a guy called Schlomo Angel, which sounds like a character from Get Shorty, rather than a figure to draw ideas for s/w architecture from!
Something that might give you more confidence is that as subversion is self-hosting, much of what you would test on "real code" is being done every day by the subversion team, and has been for months. Branching, merging, rollbacks, etc would have to be pretty rock solid by now, otherwise the SVN team wouldn't be able to self-host effectively.
But extreme pessimism for the first couple of "checkout-edit-compile-test-release-commit" cycles wouldn't hurt either - just don't expect to be shocked at issues.
I think this alpha stage is more about getting a wider audience using SVN, and give feedback on usability, rather than stability and correctness. Things like how noisy is it, how informative, can a oft-repeated three-step process be reduced to two, or one (or none!) with a little thought for SVN's activites. Stuff that comes up when code is released into the wild.
Slashdot Mirror
So they want to have copyright to stuff they dont produce - then produce something they dont want.
Take a truly distasteful photo featuring a Ford - I'm sure I dont have to give hints.
Post it somewhere.
Then complain to everyone about Ford being the copyright holder to online filth.
Do we expect them to fight for this, once they realise they have no control over what their claiming ?
Problem fixed.
Inkjet is vastly inferior to laser in every measure except cost/page.
For their larger version, it is slow. Our new full colour continuous feed laser (not sheet feed, we have a cutter and merger to create the sheets) does over 1000 pages per minute. If your going to go into commercial bureau-style printing, inkjet will never give you the quality you need to blow customers socks off.
A6 is about as big as your hand...double the length to get the A4 length means ~75 pages per minute - nothing to write home about. We have new full colour inkjets here that print thousands of feet per minute - then again their about 12 metres long, so not really for your SOHO market.
according to Novell and SCO, SCO has the licence to develop and sub-license development of Unix V ( I paraphrase from Bruce Perens comments) - so isn't this what M$ bought - a sub-license to develop Unix V ? They didn't buy a licence for Linux as far as I am aware (which isn't a lot)
I know I have buckleys of a reply - I am comment 1108 -(
Christopher Alexander et al (who wrote A Pattern Language, which inspired the GoF to write Design Patterns), stated that one could create a design by 'stringing' patterns together, but that that the result would be 'loose' and unsatisfying. The GoF themselves state that sequentially applying patterns is probably inappropriate as well. Alexander then states that designs that feature overlying and complementing patterns in the same space result in 'a profound effect'. The GoF agree with this too. However, it is implicit that inappropriate overlying or coupling will result in somethind 'profoundly bad'.
OTOH, one of the original authors of 'A Pattern Language' was a guy called Schlomo Angel, which sounds like a character from Get Shorty, rather than a figure to draw ideas for s/w architecture from!
Something that might give you more confidence is that as subversion is self-hosting, much of what you would test on "real code" is being done every day by the subversion team, and has been for months. Branching, merging, rollbacks, etc would have to be pretty rock solid by now, otherwise the SVN team wouldn't be able to self-host effectively.
But extreme pessimism for the first couple of "checkout-edit-compile-test-release-commit" cycles wouldn't hurt either - just don't expect to be shocked at issues.
I think this alpha stage is more about getting a wider audience using SVN, and give feedback on usability, rather than stability and correctness. Things like how noisy is it, how informative, can a oft-repeated three-step process be reduced to two, or one (or none!) with a little thought for SVN's activites. Stuff that comes up when code is released into the wild.
freedom of speech is not protected in the australian constitution. in fact, very little is