I tend to prototype using STL and then redesign performance critical areas.
The good choice of design patterns help reduce the complexity and bug count.
Heigh performance/ low footprint techniques such as copy on modify and lock pre-emption can ?easly? be coded in C/C++, but you need a whole framework that is far out of the reach of STL &co.
You can get optical pickups for playing vinal records which are of a far lower power than the lazers used to read CD's.
Both CD's and vinal will degrade but the CD's will degrade more than vinal, CDR's will degrade even more.
Some level of loss will always be acceptable when archiving data.
Digitally storing paintings or pictures will loose some of the original information, but an acceptable repotuction can still be reproduced.
Books can be stored without full formatting information and with corrected spelling mistakes.
Even the data set for financial and personal data will be reduced, either by picking demographic regions e.g. zip codes, or summerizing the data per hour/day/week etc....
After 50 years who cares at what microsecond the transaction was performed.
1: MAN pages are like RFC's: it takes a while to work out how there written and what information they provide, but they tend to be consistant.
2: If you don't have a clue what the documentation is talking about then either look it up or don't touch anything that is anywhere nere a production system, because YOU DON'T KNOW WHAT YOUR DOING.
3: Once you know what your doing the man pages are quite easy to follow. You don't need to be an expert, just proficient in looking things up and working out whats going on in a logical manner.
the latest kde packages (3.1.3) are still marked unstable in portage, so unless you want to compile KDE twice in a week wait until the kde packages move to stable.
Well from the chuff in the story it look like 'yet another sco v linus' slashdot artical.
The fact that IBM has evenetually responded to the allocations that SCO has made over the past few months if very important and more-or-less blows the worries of any users out of the window:(IBM will settle the issue)
if tax is 10% (i wish!) and the government spends $1million internally then it gets 100,000 back.
You also get a skilled workforce which will lead to inward investment (or so the theory goes)
A little oversimplified but you still get more for your money.
I've never seen anyone have problems using linux, and I have a lot of parties with people in... umm... various states of medication often wanting to use the computer.
Whats the cost to Australia of all that money going to the USA when some of the money could go to employee people in Australia to make OSS practical for all aplications?
USA gets less money Australian unemployement goes down.
Hey, I'll sell you the apple I've just eaten and remixed if you want. I'll even sell you apple pie and cider. and if your really getting fussy there's always the first rule of thermodynamics
I tend to prototype using STL and then redesign performance critical areas.
The good choice of design patterns help reduce the complexity and bug count.
Heigh performance/ low footprint techniques such as copy on modify and lock pre-emption can ?easly? be coded in C/C++, but you need a whole framework that is far out of the reach of STL &co.
umm, try delphi.
the C++ Builder UI is the Delphi UI, which is written in delphi.
Dig around the borland archives if you don't belive me.
Where the GPU is 128bits and the processor 32bit.
Remeber the 64bit games consoles?
I wouldn't mind using base then for Mega, Kilo etc...
when a bit is a decibyte.
....and the copyright hasn't expired yet.
When are they doing a version of jungle book?
You can get optical pickups for playing vinal records which are of a far lower power than the lazers used to read CD's.
Both CD's and vinal will degrade but the CD's will degrade more than vinal, CDR's will degrade even more.
Some level of loss will always be acceptable when archiving data.
Digitally storing paintings or pictures will loose some of the original information, but an acceptable repotuction can still be reproduced.
Books can be stored without full formatting information and with corrected spelling mistakes.
Even the data set for financial and personal data will be reduced, either by picking demographic regions e.g. zip codes, or summerizing the data per hour/day/week etc....
After 50 years who cares at what microsecond the transaction was performed.
the internet?
I can't be bothered to get them out the box, It's quicker to download the mp3.
I know some on them stopped working a few years ago when the metal layer oxidised.
So, CD's arn't lossy compression, finally I can ditch my vinal collection.
Yes I still have some CD's and a few of them are from the 80's.
I couldn't tell you if they work or not, because all the music I play is in MP3 format.
Why look for a 50 year solution, when in 20 years the archives will be stored on more efficient media, just like mp3's.
A bar code the size of the universe!!!!!
USB is still a bit flaky, anything using USB devio could have problems, and ISO transfers don't work.
The correct answer is, when we think it's about ready.
the 2.4 kernel still isn't "done".
I call him Gentoo and Kazaa.
The industries are very heverly requlated in the UK, and now we pay tax on fuel.
Using Samba, Second Edition
Samba Unleashed (Unleashed)
At least the documentation is better than most of the documentation you get with windows.
1: MAN pages are like RFC's: it takes a while to work out how there written and what information they provide, but they tend to be consistant.
2: If you don't have a clue what the documentation is talking about then either look it up or don't touch anything that is anywhere nere a production system, because YOU DON'T KNOW WHAT YOUR DOING.
3: Once you know what your doing the man pages are quite easy to follow. You don't need to be an expert, just proficient in looking things up and working out whats going on in a logical manner.
ls /usr/portage/kde-base/kdelibs/kdelibs-3.1.3* ....l d
kdelibs-3.1.3-r1.ebuild
kdelibs-3.1.3.ebui
Because the gentoo packages are/were still unstable.
If you want a ?stable? system then you will be rebuilding kde some time soon.
the latest kde packages (3.1.3) are still marked unstable in portage, so unless you want to compile KDE twice in a week wait until the kde packages move to stable.
Can't think of anything else to wait on though.
I though every one knew that EVIL BOBs (bitmap object) come in the BMP format, they even started off life twisted.
Well from the chuff in the story it look like 'yet another sco v linus' slashdot artical.
The fact that IBM has evenetually responded to the allocations that SCO has made over the past few months if very important and more-or-less blows the worries of any users out of the window:(IBM will settle the issue)
if tax is 10% (i wish!) and the government spends $1million internally then it gets 100,000 back.
You also get a skilled workforce which will lead to inward investment (or so the theory goes)
A little oversimplified but you still get more for your money.
I've never seen anyone have problems using linux, and I have a lot of parties with people in... umm... various states of medication often wanting to use the computer.
Whats the cost to Australia of all that money going to the USA when some of the money could go to employee people in Australia to make OSS practical for all aplications?
USA gets less money
Australian unemployement goes down.
Whats wrong with OSS for sally?
Hey,
I'll sell you the apple I've just eaten and remixed if you want.
I'll even sell you apple pie and cider.
and if your really getting fussy there's always the
first rule of thermodynamics
Lets say someone stole an apple.
Apples are free, they grow on trees.
The real loss is the cost of the labour in getting the apple to the shops and selling it.
If someone downloads music then the media is free, the cost of music is in the labour it takes to produce it.
What's the differance?
Laws aren't supposted to 'protect the majority from the minority', infact the oposite, laws are supposed to protect the weak.
In this case the RIAA are weak and people are strong.