It's a kind of marketing. It's probably someone with a vested interest in itanic (from HP, Compaq, Dell or intel) trying to spread FUD about the "demise" of current working, available, better 64-bit processors (like PA-RISC, PowerPC, MIPS, UltraSPARC, Alpha etc.) to make the less well informed geek community think that itanic is the future. Unfortunately, they're 3 years too late and everyone sees right through them.
...and it has the advantage of a negligable hang-over (ie 5 orders of magnitude less)
but you can't beat red wine.
Well, you can beat me over the head with a LART.
No, I disagree. It's definitely heading towards being a surveilance/police state, as is the UK.
They're talking about centrally-monitored CCTV in your house "for safety and to deter criminals"
This is and absolutely outrageous state of affairs. The USA is becoming a police state. I thought it was supposed to be a paragon of virtue and freedom by which all other nations should measure themselves?
As more cases like this arise and more people complain, the DMCA will eventually be seen for what it is, even by those ignorant or greedy fools who supported it.
It is complete madness and it will surely be wiped from the statute books.
You can eliminate PCI bus contention issues by hanging several drives off of a fast wide SCSI card e.g. U160. it works very well for hard disk striping.
Well, I started on a ZX81 (8-bit Z80 with 1K RAM - you read that right).
I remember the disillusionment when business and the world passed the Amiga and ST by in favour of the inferior IBM PC architecture.
I remember when Microdrive meant a tiny storage device that took cartridges of tape, holding a whopping 85K of data.
I remember when printer were dot matrix (9-pin) and spoke RS-232, and made my own cable.
I remember POKE'ing machine code in to a REM statement in the program using a hex loader (put in from memory).
I remember when 16-bit machines were huge.
I remember when 256 colours were incredible.
I remember when you needed hours of mainframe time to do wireframe 3D.
I remember when BASIC was scoffed at and no one would dream of writing a database client in it.
I remember when FORTH was the language of choice.
I remember when ASCII wasn't a de-facto standard.
I remember when there was no hardware multiply.
I remember when everyone had their own floating point in software.
I remember when serious engineers used a 386 with a 387.
I'm 27 years old.
Good. That's exactly what I'll do. I don't even have a TV card in any of my machines. A friend of mine said, "a lot of people do not posess MOT certificates, but they don't send people round to check if they're operating a car illegally."
Ah, no where is this more evident that at the traditional Brtish fisch and chip shop. At least we've got a clue now and adopted chicken tikka masala as our national dish:-)
The depressing thing is, that here in the UK they do similar things (to the BSA) with television licenses. Since I grew up and left home, I have never posessed a TV, yet they still insist on sending threatening letters every few months and someone to "inspect" my premises for an illegal television, or TV receiving equipment.
So why did Bach decide to have "equally tempered" scales, and where did all the modes go too?
Isn't it like saying, in cooking, we have all these herbs and spices, they're too difficult for me, lets throw them out and make everything taste the same?
It's true that there's been a lot of software bloat, but other developments have been quite nice.
Operating Systems have become much more sophisticated to the point where multi-user mult-tasking network-aware ones are ubiquitous.
Networking has improved.
User Interfaces have become more friendly.
Think of all those 24-bit images and CD quality sound samples and the amount of space they take up.
It's also much nicer to have the document you're working on appear with colours and fonts etc.
The problem is a lot of the bloat comes from people paying less attention to optimising their code, using better algorithms etc. The other place it comes from is hauling around legacy API's and ABI's so that you can run 20-year-old software.
For many years there was a mindset that if your machine didn't run Lotus 1-2-3 v1 or 2 it was no use (hence why my dad wouldn't buy me an Amiga or ST back in the day... not that I'm bitter -: )
So, we have umpteen standards, API's, ABI's binary formats, document formats etc. and they all need to we supported and converted between.
I wonder if everyone had adopted, say, RTF for word processor documents 20 years ago, how much trouble and code could have been saved...
...but now I digress.
In an ideal world, you'd have something like Java with everything connected to the "network" and objects floating about to do things. Your machine would just get the objects it required to do a certain thing etc. etc....
Yes, I had a Spectrum 128 and a microdrive.
I used to compile my C programs off it. I had HiSoft C (integer only, K&R) and it could compile from microdrive to RAM. It was hellishly unreliable and I had to make 4 copies of everything. Anyway, it was an order of magnitude cheaper than a floppy drive and interface. I got my interface 1 and microdrive for 50 quid.
I wrote a primitive window and menu library in C and tried to sell it to HiSoft to get enough money to buy an Amiga or ST but, alas, it wasn't to be.
At 14 I wasn't old enough to get a part-time job to fund my computing habbit.
So I was stuck with the Spectrum and my dad's Compaq SLT/286 laptop (12MHz, 1 MB RAM, 640x480 16-shades of grey LCD, 20MB hard drive) and Lattice C.
There must be hundreds or thousands of legacy applications out there built to use Motif. Having a reference like this will be invaluable for those poor souls who have to maintain those pieces of code. Just because it's old and there are many more modern alternatives available doesn't automatically make it irrelevant.
One way might be to identify "features" in the image e.g. by colour, brightness or changes and build an association tree.
Basically, identify all "peaks" (whatever feature you're interested in) and sort them. Start with the most outstanding feature and associate its nearest neighbours with it. Repeat many times. You will have data structure of references which will produce a map of islands and isthmuses depending on how far down you look.
Attach a "label" (unique ID) to each significant feature in the frame.
Repeat for the next frame.
Compare significant features. Using some sort of threshold, you can attach a confidence level that you're looking at the safe feature in the previous frame.
That's a simplistic overview, but I did it many years ago for looking at the output of stellar formation simulations.
Re:Humm... aren't they a bit late?
on
Intel's Big Chip
·
· Score: 0
What amazes me is that there are already tried-and-tested 64-bit machines on the market with reliability, scalability, and dare I say it, at lower cost....
...and yet people seem to look at this itanic as if it's the answer to their prayers.
Ho hum.
Slashdot Mirror
Think of it as the action of one dancer triggering off the action in another and so forth, like a chain reaction.
It's a kind of marketing. It's probably someone with a vested interest in itanic (from HP, Compaq, Dell or intel) trying to spread FUD about the "demise" of current working, available, better 64-bit processors (like PA-RISC, PowerPC, MIPS, UltraSPARC, Alpha etc.) to make the less well informed geek community think that itanic is the future. Unfortunately, they're 3 years too late and everyone sees right through them.
...and it has the advantage of a negligable hang-over (ie 5 orders of magnitude less)
but you can't beat red wine.
Well, you can beat me over the head with a LART.
No, I disagree. It's definitely heading towards being a surveilance/police state, as is the UK.
They're talking about centrally-monitored CCTV in your house "for safety and to deter criminals"
>Wake up, rub yer eyes and smell the coffee, this is a police state. Maybe it hasn't affected you yet, but rest assured, it sure as hell will.
It sure as hell will if Tony Blair copies ol' W.
This is and absolutely outrageous state of affairs. The USA is becoming a police state. I thought it was supposed to be a paragon of virtue and freedom by which all other nations should measure themselves?
As more cases like this arise and more people complain, the DMCA will eventually be seen for what it is, even by those ignorant or greedy fools who supported it.
It is complete madness and it will surely be wiped from the statute books.
"Open Source" is not a single group of people.
Therefore such an idea is ridiculous.
I take it you're new to this game?
And pray tell, how does the 16-bit nature of the Z80 addressing help when used with >5 GB (5*2^30) data?
You can eliminate PCI bus contention issues by hanging several drives off of a fast wide SCSI card e.g. U160. it works very well for hard disk striping.
AFAICR gcc's IA-64 output runs at 13% of the speed of intel's IA-64 compiler.
Well, I started on a ZX81 (8-bit Z80 with 1K RAM - you read that right).
I remember the disillusionment when business and the world passed the Amiga and ST by in favour of the inferior IBM PC architecture.
I remember when Microdrive meant a tiny storage device that took cartridges of tape, holding a whopping 85K of data.
I remember when printer were dot matrix (9-pin) and spoke RS-232, and made my own cable.
I remember POKE'ing machine code in to a REM statement in the program using a hex loader (put in from memory).
I remember when 16-bit machines were huge.
I remember when 256 colours were incredible.
I remember when you needed hours of mainframe time to do wireframe 3D.
I remember when BASIC was scoffed at and no one would dream of writing a database client in it.
I remember when FORTH was the language of choice.
I remember when ASCII wasn't a de-facto standard.
I remember when there was no hardware multiply.
I remember when everyone had their own floating point in software.
I remember when serious engineers used a 386 with a 387.
I'm 27 years old.
Good. That's exactly what I'll do. I don't even have a TV card in any of my machines. A friend of mine said, "a lot of people do not posess MOT certificates, but they don't send people round to check if they're operating a car illegally."
Ah, no where is this more evident that at the traditional Brtish fisch and chip shop. At least we've got a clue now and adopted chicken tikka masala as our national dish :-)
Very interesting!
Could you please give me some links (google is not my friend -: )
The depressing thing is, that here in the UK they do similar things (to the BSA) with television licenses. Since I grew up and left home, I have never posessed a TV, yet they still insist on sending threatening letters every few months and someone to "inspect" my premises for an illegal television, or TV receiving equipment.
So why did Bach decide to have "equally tempered" scales, and where did all the modes go too?
Isn't it like saying, in cooking, we have all these herbs and spices, they're too difficult for me, lets throw them out and make everything taste the same?
Thanks.
It's amazing that this sort of thing was being done 40 years ago. So, what comes after OOP?
It's true that there's been a lot of software bloat, but other developments have been quite nice.
Operating Systems have become much more sophisticated to the point where multi-user mult-tasking network-aware ones are ubiquitous.
Networking has improved.
User Interfaces have become more friendly.
Think of all those 24-bit images and CD quality sound samples and the amount of space they take up.
It's also much nicer to have the document you're working on appear with colours and fonts etc.
The problem is a lot of the bloat comes from people paying less attention to optimising their code, using better algorithms etc. The other place it comes from is hauling around legacy API's and ABI's so that you can run 20-year-old software.
For many years there was a mindset that if your machine didn't run Lotus 1-2-3 v1 or 2 it was no use (hence why my dad wouldn't buy me an Amiga or ST back in the day... not that I'm bitter -: )
So, we have umpteen standards, API's, ABI's binary formats, document formats etc. and they all need to we supported and converted between.
I wonder if everyone had adopted, say, RTF for word processor documents 20 years ago, how much trouble and code could have been saved...
...but now I digress.
In an ideal world, you'd have something like Java with everything connected to the "network" and objects floating about to do things. Your machine would just get the objects it required to do a certain thing etc. etc....
Yes, I had a Spectrum 128 and a microdrive.
I used to compile my C programs off it. I had HiSoft C (integer only, K&R) and it could compile from microdrive to RAM. It was hellishly unreliable and I had to make 4 copies of everything. Anyway, it was an order of magnitude cheaper than a floppy drive and interface. I got my interface 1 and microdrive for 50 quid.
I wrote a primitive window and menu library in C and tried to sell it to HiSoft to get enough money to buy an Amiga or ST but, alas, it wasn't to be.
At 14 I wasn't old enough to get a part-time job to fund my computing habbit.
So I was stuck with the Spectrum and my dad's Compaq SLT/286 laptop (12MHz, 1 MB RAM, 640x480 16-shades of grey LCD, 20MB hard drive) and Lattice C.
...and Miguel is a baboon.
There must be hundreds or thousands of legacy applications out there built to use Motif. Having a reference like this will be invaluable for those poor souls who have to maintain those pieces of code. Just because it's old and there are many more modern alternatives available doesn't automatically make it irrelevant.
One way might be to identify "features" in the image e.g. by colour, brightness or changes and build an association tree.
Basically, identify all "peaks" (whatever feature you're interested in) and sort them. Start with the most outstanding feature and associate its nearest neighbours with it. Repeat many times. You will have data structure of references which will produce a map of islands and isthmuses depending on how far down you look.
Attach a "label" (unique ID) to each significant feature in the frame.
Repeat for the next frame.
Compare significant features. Using some sort of threshold, you can attach a confidence level that you're looking at the safe feature in the previous frame.
That's a simplistic overview, but I did it many years ago for looking at the output of stellar formation simulations.
What amazes me is that there are already tried-and-tested 64-bit machines on the market with reliability, scalability, and dare I say it, at lower cost....
...and yet people seem to look at this itanic as if it's the answer to their prayers.
Ho hum.
Miguel de Icaza adopts .NET as the foundation upon which future releases of GNOME will be build?