Sheesh. Of all the slop that gets posted on/. I can't figure out what magic fscking criteria this question made in order to get accepted. Duh! use FRESHMEAT.NET to find this sort of thing out. Maybe just grab a brain and first check out ghostscript. Fsck!!!
Thatalmost all of Slashdot reade^H^H^H^H^H posters are for the most part, ignorant of the facts, and completely biased. (No suprise there...)
1.Microsoft's.NET platform is NOT about 'running' Office at the server, and pay per use. Forget about it. Jesus Fscking Christ.
2.It is (largely) about building applications on a common framework. This framework supports XML,SOAP,umpteen languages,a better VM bytecode than JAVA and,.... and....
3.Microsoft has submitted C# and the.NET CLR to ECMA for standardization. And commited to following the ECMA standards in their own product.
SUNAsked for Java to be standardized, with the stipulation that they would control the process and could veto anything.
Now, weather you want to use.NET or not, or use Java or not, there are many virtues one way or another, but It is apparent that the majority of the FUD spread from here is flowing from the 'anti-ms' side.
I would Highly recommend you take a wide berth around that god forsaken JDOM. In addition to them changing the API's quite significantly between betas, and the utter lack of usable documentation, they code up stub methods for anything they havn't implemented, and don't tell you what is not complete.
As it is, parsing text is one of the things that java does the absolute worst, as it's string management is an abyssmal. Your best bet is to make your choice based on what your goals for your documents are.
1. Are you going to need to evaluate information in your XML documents linearly, or random-access. If you are just reading thru the document, and don't need to keep a tree, use SAX. Very Simple, Very Straightforward interface...
2. Are you going to need to access the same document several times? Use DOM, and cache the document in memory.
3. Are your documents LARGE?... go back to SAX, that DOM thing can use HUGE chunks of ram...
4. Read Read Read Download several Parsers, try them out, _Understand_ the way this technology works, and then benchmark your typical use of the technology with several parsers and methods. Depending on how you use this technology, and it's implementation is going to be as important as the flavor of parser. Do you Need to validate your documents? How many are you going thru? how fast does it need to be. These questions change the answer for 'which parser to use' drastically.
And remember: XML is NOT the magic bullet. For pete's sake, it's bloody text parsing... It's not designed to be ultra fast, it is designed to be flexible...
Are there any PCMCIA based Graphics cards out there? Are There any that are also 3D accellerators?
I Always wondered why 3dfx never made one of thier goofy pass-thru video cards in a PCMCIA form factor. Laptop users could really benefit.
That Zoomed Video Port Crap many manufacturers were so fscking enamoured about could have even provided a pathway to the video ram that could support 3d accellerators.
if WE all TYPED our messages like ANDRE HEDRICK things would BE VERY scary!;)
I've worked with a couple of people who were involved on the Project for the Olympics @ syndey. These were not what you would exactly call rocket-scientists. More like brain surgeons( ala Sean from survivor. Sheesh! ) None of these monkeys had even a remote idea what kind of standards the pages were to be coded against. It is not so much the use of technologies that are not supported on each platform, as to not a clue as to what HTML is for. Trust me, it will take about a million dollars to do it if IBM is involoved. Probably two guys, 8 hours , with Emacs could get the job done.
Grrrr
I registered a domain not too long ago, and I was a little suprised that their online method of credit card payment was completely unsecured. Considering that these bozos apparently have no idea what secure systems are about, I was very disapointed.
As far as I can remember, they were at the same time, pimping someone else's secure-e-commerce solution. Un-fscking-believable.
You know, for a long time, I've been not too terribly concerned with the US government's activities when related to 'spying' on it's populace.
For the first time, I am now moving off of that position, as if this little factiod is true, it really means that we should all be a little more scared about the personal freedoms we enjoy.
I'm a little shocked. And a little outraged. This has got to be the most strong argument for Open Source/Free Software that I've ever seen. This sort of thing would^h^h^h^h^h couldn't happen if there were a million peers viewing the source.
Slashdot Mirror
Sheesh. Of all the slop that gets posted on /. I can't figure out what magic fscking criteria this question made in order to get accepted. Duh! use FRESHMEAT.NET to find this sort of thing out. Maybe just grab a brain and first check out ghostscript. Fsck!!!
That almost all of Slashdot reade^H^H^H^H^H posters are for the most part, ignorant of the facts, and completely biased. (No suprise there...)
.NET platform is NOT about 'running' Office at the server, and pay per use. Forget about it. Jesus Fscking Christ.
.NET CLR to ECMA for standardization. And commited to following the ECMA standards in their own product.
.NET or not, or use Java or not, there are many virtues one way or another, but It is apparent that the majority of the FUD spread from here is flowing from the 'anti-ms' side.
1.Microsoft's
2.It is (largely) about building applications on a common framework. This framework supports XML,SOAP,umpteen languages,a better VM bytecode than JAVA and,.... and....
3.Microsoft has submitted C# and the
SUNAsked for Java to be standardized, with the stipulation that they would control the process and could veto anything.
Now, weather you want to use
I would Highly recommend you take a wide berth around that god forsaken JDOM. In addition to them changing the API's quite significantly between betas, and the utter lack of usable documentation, they code up stub methods for anything they havn't implemented, and don't tell you what is not complete.
... go back to SAX, that DOM thing can use HUGE chunks of ram...
As it is, parsing text is one of the things that java does the absolute worst, as it's string management is an abyssmal. Your best bet is to make your choice based on what your goals for your documents are.
1. Are you going to need to evaluate information in your XML documents linearly, or random-access. If you are just reading thru the document, and don't need to keep a tree, use SAX. Very Simple, Very Straightforward interface...
2. Are you going to need to access the same document several times? Use DOM, and cache the document in memory.
3. Are your documents LARGE?
4. Read Read Read Download several Parsers, try them out, _Understand_ the way this technology works, and then benchmark your typical use of the technology with several parsers and methods. Depending on how you use this technology, and it's implementation is going to be as important as the flavor of parser. Do you Need to validate your documents? How many are you going thru? how fast does it need to be. These questions change the answer for 'which parser to use' drastically.
And remember: XML is NOT the magic bullet. For pete's sake, it's bloody text parsing... It's not designed to be ultra fast, it is designed to be flexible...
A few words from me.
Are there any PCMCIA based Graphics cards out there?
;)
Are There any that are also 3D accellerators?
I Always wondered why 3dfx never made one of thier goofy pass-thru video cards in a PCMCIA form factor. Laptop users could really benefit.
That Zoomed Video Port Crap many manufacturers were so fscking enamoured about could have even provided a pathway to the video ram that could support 3d accellerators.
if WE all TYPED our messages like ANDRE HEDRICK things would BE VERY scary!
I've worked with a couple of people who were involved on the Project for the Olympics @ syndey. These were not what you would exactly call rocket-scientists. More like brain surgeons( ala Sean from survivor. Sheesh! )
None of these monkeys had even a remote idea what kind of standards the pages were to be coded against. It is not so much the use of technologies that are not supported on each platform, as to not a clue as to what HTML is for.
Trust me, it will take about a million dollars to do it if IBM is involoved. Probably two guys, 8 hours , with Emacs could get the job done. Grrrr
You know, with enough of those things, I bet you could make a great beowulf cluster! G
As far as I can remember, they were at the same time, pimping someone else's secure-e-commerce solution. Un-fscking-believable.
G
grin
For the first time, I am now moving off of that position, as if this little factiod is true, it really means that we should all be a little more scared about the personal freedoms we enjoy.
I'm a little shocked. And a little outraged. This has got to be the most strong argument for Open Source/Free Software that I've ever seen. This sort of thing would^h^h^h^h^h couldn't happen if there were a million peers viewing the source.
Un-fscking-beliveable..
*long live linux*