True. Also, for firewalls, and other embedded systems, dual-CPU's can be a hinderance. Single CPUs work well with Storage devices and file servers. Of course, for all of these devices, who needs a 1.5Ghz CPU! File servers are all about memory, and fast hard drives.
Intel is blowing it big time here. The single cpu desktop market is over-saturated! Inventories are way too high! Its the server chips that are in demand. A single CPU server is like... well... crap.
Who needs OSHA? Shouldn't the full employment economy take care of these workplace issues. No one needs to work in a dangerous factory, when there are 50 other jobs available to that person. Look at developers! We pick our employers based on many factors. Imagine a startup having to comply with these rediculous ergonomic laws!
Actually, the U.S.'s predominance in the computer field is in large part due to government assistance
Rediculous. Who did the government goto for those contracts: private companies! The US's dominane in the computer field is based on the fact that our enormous economy demanded a faster, better way to do things.
The issue, though, isn't providing a new outlet for Linux fetishism. Rather, developers are keying in on the idea that Linux provides access to source code, an enthusiastic developer community, and a level of flexibility in crafting environments that doesn't exist with the competition from Microsoft and Palm. Qt/Embedded, for instance, can leverage a large body of developers already familiar with Qt, and a body of source code for desktop apps that can be ported to handhelds with tweaks for interfaces.
YES!!! Open source is the key to PDA's success. PDAs functions and rolls are so similar to embedded systems. There's a reason your router, firewall, switch, ssl-accelerator, whatever runs a hacked up BSD or linux kernel. PDAs need to maximize the hardware. Software must integrate in with the OS. The OS must be open source!
Those standards would be set by the WHO in consultation with "governments, medical associations, consumer groups, the health industry and others", it said.
I can imagine the lawsuits here. What will qualify for.health and what will not. Will a pharamcy retailer qualify for.health?
What elected person created the TCP/IP standand?
What elected person oversaw the HTTP standards?
What elected person oversaw the C++ standards?
What elected person oversaw the ANSI C standards?
What elected person oversees Java?
At the opening of the gulf war, several Apache helicopters drifted offcourse and destroyed several US tanks before realizing their mistake. The pilots were unsure if the targets were enemies, but the CommandControl AWAKs insisted the targets were enemies. Here is a case where the human factor was not helpful.
Warning: Do not stand within 6 feet of StorageArray. Keep StorageArray away from small children or pregnant mothers. Handle StorageArray with extreme caution. Always were saftey goggles when working with StorageArray. Do not taunt Storage Array.
"Throughout most of my life, I raised tobacco. I want you to know that with my own hands, all of my life, I put it in the plant beds and transferred it. I've hoed it. I've dug in it. I've sprayed it, I've chopped it, I've shredded it, spiked it, put it in the barn and stripped it and sold it."
-Al Gore
(Source: [New York] Newsday, 2/26/88
"Sometimes, you never fully face up to things that you ought to face up to."
- Al Gore
discussing why he accepted checks from his family tobacco farm and contributions from tobacco companies for years after the tragic death of his sister that he spoke about so emotionally at the 1996 Democratic convention.
(Source: "'Numbness' Let Gore Accept Tobacco Help," San Francisco Chronicle, August 30, 1996)
no doubt. What complete joke. What would be interesting, would be to explore calculations in something other than binary. For example base 3 or base 1.1.
Not litterally RPC of course. RPC is a thousand levels lower and considerably more complicated than some fancy XML schemas. However, by definition these "web services" are APIs brokered by App servers. Often, they are procedural and involve state. As you said, they're second gen EDI. I'd add DCOM and CORBA to the list. The only application I can see for these XML solutions is as translation layers, for multiple components that all speak different tounges. As you said, every time one of these things arrives on the scene, everybody claims it will universalize everything. Of course it won't universalize squat. All it will do is open the door to more developers, because XML is fair simpler than IDL.
I agree that XML is a fantastic medium to work with. But, I would prefer to limit XML to document based APIs (single request-response approaches). For anything requiring significant state, or complicated procedural calls (such as some services), I would prefer to use a procedural language such as Java. Of course, the downside to java is the required burden of your clients to run jvms. Clearly jvms are heavier than xml-parsers, and in those cases I would prefer XML. However, intricate protocols and schemas can be as complicated as an interface (at which point you say screw it and go with the interface).
All of these standards are just RPC in a text-printable XML form, that tunnels via HTTP/HTTPS. While they offer plafform independence, I would prefer a more compact and functional API to doc-based XML, such as JavaBeans and the like. These XML APIs will eventually become so confusing, that they'll require a layer above them! Not to mention, why do server to server communications need to be text readible? Isn't that wasteful?
Slashdot Mirror
I would agree with some of your points, but really the key point is that Linux isn't ready for idiots (most people).
True. Also, for firewalls, and other embedded systems, dual-CPU's can be a hinderance. Single CPUs work well with Storage devices and file servers. Of course, for all of these devices, who needs a 1.5Ghz CPU! File servers are all about memory, and fast hard drives.
Mauve makes 'em look like a sparc.
If you paint your 386 Mauve, it will perform like a P4 (and even support SMP!)
Here's an article on the .heath rejection
Intel is blowing it big time here. The single cpu desktop market is over-saturated! Inventories are way too high! Its the server chips that are in demand. A single CPU server is like... well... crap.
Who needs OSHA? Shouldn't the full employment economy take care of these workplace issues. No one needs to work in a dangerous factory, when there are 50 other jobs available to that person. Look at developers! We pick our employers based on many factors. Imagine a startup having to comply with these rediculous ergonomic laws!
Actually, the U.S.'s predominance in the computer field is in large part due to government assistance
Rediculous. Who did the government goto for those contracts: private companies! The US's dominane in the computer field is based on the fact that our enormous economy demanded a faster, better way to do things.
The issue, though, isn't providing a new outlet for Linux fetishism. Rather, developers are keying in on the idea that Linux provides access to source code, an enthusiastic developer community, and a level of flexibility in crafting environments that doesn't exist with the competition from Microsoft and Palm. Qt/Embedded, for instance, can leverage a large body of developers already familiar with Qt, and a body of source code for desktop apps that can be ported to handhelds with tweaks for interfaces.
YES!!! Open source is the key to PDA's success. PDAs functions and rolls are so similar to embedded systems. There's a reason your router, firewall, switch, ssl-accelerator, whatever runs a hacked up BSD or linux kernel. PDAs need to maximize the hardware. Software must integrate in with the OS. The OS must be open source!
Those standards would be set by the WHO in consultation with "governments, medical associations, consumer groups, the health industry and others", it said.
I can imagine the lawsuits here. What will qualify for .health and what will not. Will a pharamcy retailer qualify for .health?
e.g. 'www.amazon.health'Interesting point.
What elected person created the TCP/IP standand? What elected person oversaw the HTTP standards? What elected person oversaw the C++ standards? What elected person oversaw the ANSI C standards? What elected person oversees Java?
At the opening of the gulf war, several Apache helicopters drifted offcourse and destroyed several US tanks before realizing their mistake. The pilots were unsure if the targets were enemies, but the CommandControl AWAKs insisted the targets were enemies. Here is a case where the human factor was not helpful.
Try to get to Big Ben in London on Dec 4th, 1932.
With respect to those concerned, this book was pathetic. Any book that recommends a database written in java running in a JVM isn't worth your time.
What is the real problem here? People can't read because the're old? If you can't figure out that form, should you be voting?
The StorageEngine (4 32G disks) must talk to the StorageArray which has the 8 32G disks Combined the two get the 432G storage.
Warning: Do not stand within 6 feet of StorageArray. Keep StorageArray away from small children or pregnant mothers. Handle StorageArray with extreme caution. Always were saftey goggles when working with StorageArray. Do not taunt Storage Array.
-Al Gore
(Source: [New York] Newsday, 2/26/88
"Sometimes, you never fully face up to things that you ought to face up to."
- Al Gore
discussing why he accepted checks from his family tobacco farm and contributions from tobacco companies for years after the tragic death of his sister that he spoke about so emotionally at the 1996 Democratic convention. (Source: "'Numbness' Let Gore Accept Tobacco Help," San Francisco Chronicle, August 30, 1996)
How many digits in base pi would you need to express decimal 1.
AAHHHHHH OH MY GOD WE'RE OFF COURSE BY A METER!!! - super intelligent microbes in their tiny spaceship
no doubt. What complete joke. What would be interesting, would be to explore calculations in something other than binary. For example base 3 or base 1.1.
Not litterally RPC of course. RPC is a thousand levels lower and considerably more complicated than some fancy XML schemas. However, by definition these "web services" are APIs brokered by App servers. Often, they are procedural and involve state. As you said, they're second gen EDI. I'd add DCOM and CORBA to the list. The only application I can see for these XML solutions is as translation layers, for multiple components that all speak different tounges. As you said, every time one of these things arrives on the scene, everybody claims it will universalize everything. Of course it won't universalize squat. All it will do is open the door to more developers, because XML is fair simpler than IDL.
I agree that XML is a fantastic medium to work with. But, I would prefer to limit XML to document based APIs (single request-response approaches). For anything requiring significant state, or complicated procedural calls (such as some services), I would prefer to use a procedural language such as Java. Of course, the downside to java is the required burden of your clients to run jvms. Clearly jvms are heavier than xml-parsers, and in those cases I would prefer XML. However, intricate protocols and schemas can be as complicated as an interface (at which point you say screw it and go with the interface).
All of these standards are just RPC in a text-printable XML form, that tunnels via HTTP/HTTPS. While they offer plafform independence, I would prefer a more compact and functional API to doc-based XML, such as JavaBeans and the like. These XML APIs will eventually become so confusing, that they'll require a layer above them! Not to mention, why do server to server communications need to be text readible? Isn't that wasteful?