This is is a good thing. That way you can manipulate it with the DOM, parse it with SAX, transform it with XSLT, etc. You never need to write annother parser.
Humongous bloat.
If you're referring to features... SVG is only part of the standards you need, it's finely tuned to doing Scalable Vector Graphics, nothing else.
If you're referring to download speed, refer to this.
You fail to understand the role of SVG. SVG does vector graphics. Other standards do their own job.
The browser parses XML (Gecko/IE5.5). The xml can be inline in the page, linked with an invisible object tag, or fetched with XMLHTTPRequest. It can even be a response to an XML-RPC query made with XMLHTTPRequest.
JavaScript is the scripting language (NN4/IE4).
CSS2 does layout (Gecko/IE6). It can be modified dynamically with JavaScript.
DOM2 (Gecko/IE6) is the interface that allows you to change the content of your page.
XMLHTTPRequest (Gecko) (or alternately, ActiveXObject("Msxml2.XMLHTTPRequest")(IE 6) ) is the object that allows you to push data to the application. Browser doesn't support either? document.write() an invisible iframe.
setTimeout(functionref,delay)(NN4/IE4) is the JavaScript function that allows you to do anything periodically including refresh the data
object (Gecko/IE5.5) is the html tag that lets you embed video (or anything else) in web pages.
Other than SVG (which is coming soon), I can guarantee that it'll run on a decent number of browsers (IE 6, Netscape 7, Camino, Mozilla 1.3, Galeon, Beonex, CompuServe 7, K-Meleon, Aphrodite, etc). If you study the standards a little, you'll see that each one does it's own job, and does it well. There is no one w3c standard to do everything because not all applications need to do everything (ie, html in email is nice, but JavaScript in email is dangerous).
Ummm, SVG is a dialect of XML. Any SVG rendering engine has an XML Parser. It is intended to do Scalable Vector Graphics only, hence the name. If you need Video, that's what ogg Theora, MPEG4, etc are for.
If you honestly believe that JavaScript, CSS, and DOM are "hopelessly inadequate when it comes to serving up dynamic content and developing web-based applications" I suggest you read Inner-Browsing:Extending Web Browsing the Navigation Paradigm on Netscape DevEdge and/or pick up a good recent book on XHTML, CSS, DOM2, and JavaScript.
Actually, my estimate was extremely conservative to start with. A better estimate would be that KDE already has it in KDE 3.2 Beta 1, so they'll likely have it in non-beta in a month or two.
As for when "Longhorn" comes out, I think it'll probably be sooner than everyone expects, but be extremely buggy, or nowhere as feature complete as they claim, as they rush to re-label WinXP and add a little glitz to the UI. Alternatively, it may never be released as such as they use "Longhorn" as a code word for "we're just floating this feature idea to see if anyone likes it and we may never implement it".
r00t@localhost# emerge zig
...
the system is going down for fdisk now!
Operator@othermachineacrosstheroom$ mirc
\chan gentoo Operator:Take zig-0.1.0 off the server now!!!!!!!!! Captain: What happen? Operator: Somebody set up us the bomb. Operator: We get signal. Captain: What! Operator: Main screen turn off. Cats::P Captain: It's You!! Cats: How are you gentlemen!! Cats: All your code base are belong to us. Cats: You are on the way to destruction. Captain: What you say!! Cats: You have no chance to survive make your time. Cats: ROFLMAO Captain: emerge -C "zig" Captain: You know what you doing. Captain: mv ~gentoo/public/"zig". Captain: For great justice.
You're on crack... what's the difference between emerge and apt-get from a security standpoint? In both you don't actually inspect the code before it's installed on your machine. You have to trust the repository admin for both systems.
Gentoo is really cool for producing systems optimized exactly for your system, making sure you have the official version of programs, and knowing that a package will be linked against the correct minor version of libraries. What it doesn't do is inspect the sourcecode for you.
All of the vulnerabilities I listed made it into official releases before being patched. The bug this story is about didn't make it one day in the source tree, let alone into an official release.
Sorry about the Protegrity one, I must've linked the wrong one. I was looking for this one (the one exploited by the slammer worm).
Slashdot Mirror
Commercial manufacturers silkscreen their CDs, they don't use adhesive labels.
All media degrades. The trick is to use redundant data, and re-copy it before the media is expected to fail.
I've not tried Solaris, but my top (bottom?) pick would be Windows ME
I strongly suspect that all IBM's inter-site IP traffic flows through Encrypted VPNs.
It's probably OpenH323. IBM is smart, they wouldn't bother to re-invent the wheel ... err ... gateway
OpenH323 for more info about VoIP PBX whatevers... or GnomeMeeting for a client so you can start getting your hands dirty now...
This is is a good thing. That way you can manipulate it with the DOM, parse it with SAX, transform it with XSLT, etc. You never need to write annother parser.
If you're referring to features... SVG is only part of the standards you need, it's finely tuned to doing Scalable Vector Graphics, nothing else.
If you're referring to download speed, refer to this.
1 2 3
Development of flash player for environments other than the latest version of MS Windows on x86 is glacially slow.
what's more, SVG is useful in settings other than web pages, such as desktop publishing.
Incorporate {Scalable Vector Graphics} into {w3c standards compliant open source web rendering engine} and add {Synchronized Multimedia Integration Language} with support for mp3 and/or {Audio compression and streaming that isn't patent encumbered}.
See This Comment.
POST /xml-rpc/PatientRecords HTTP/1.0
...
< string>Severe hemmorage untreatable by dressing.</string></value> ...
m g src="http://ads.example.com/images/censorware.gif" ><br />
User-Agent: PatientRecordsApp
Host: hospital.example.org
Content-Type: text/xml
Content-length: foo
<?xml version="1.0"?>
<methodCall> <methodName >Waitlist.BookSurgery</methodName > <params><param><struct>
<member>
<name>PatientID</name>
<value><i4 >2323434</i4 ></value>
</member>
<member>
<name>Priority-Reason</name>
<value>
</member>
</struct></param ></params ></methodCall>
HTTP/1.1 200 OK
Connection: close
Content-Type: text/html
<html><head></head><body>
<a href="http://ads.example.com/censorware.asp">
<i
<blink>Get your censorware now!!!</blink></a>
</body></html>
Other than SVG (which is coming soon), I can guarantee that it'll run on a decent number of browsers (IE 6, Netscape 7, Camino, Mozilla 1.3, Galeon, Beonex, CompuServe 7, K-Meleon, Aphrodite, etc). If you study the standards a little, you'll see that each one does it's own job, and does it well. There is no one w3c standard to do everything because not all applications need to do everything (ie, html in email is nice, but JavaScript in email is dangerous).
Standards would be better suited to programming. XML makes a lousy object-oriented imperative programming language, and a lousy audio/video codec.
Ummm, SVG is a dialect of XML. Any SVG rendering engine has an XML Parser. It is intended to do Scalable Vector Graphics only, hence the name. If you need Video, that's what ogg Theora, MPEG4, etc are for.
If you honestly believe that JavaScript, CSS, and DOM are "hopelessly inadequate when it comes to serving up dynamic content and developing web-based applications" I suggest you read Inner-Browsing:Extending Web Browsing the Navigation Paradigm on Netscape DevEdge and/or pick up a good recent book on XHTML, CSS, DOM2, and JavaScript.
Actually, my estimate was extremely conservative to start with. A better estimate would be that KDE already has it in KDE 3.2 Beta 1, so they'll likely have it in non-beta in a month or two.
As for when "Longhorn" comes out, I think it'll probably be sooner than everyone expects, but be extremely buggy, or nowhere as feature complete as they claim, as they rush to re-label WinXP and add a little glitz to the UI. Alternatively, it may never be released as such as they use "Longhorn" as a code word for "we're just floating this feature idea to see if anyone likes it and we may never implement it".
They have something to refer to. You haven't read the link I posted, have you?
Just in time to be 4-5 years behind KDE, which will likely have this within 6 to 12 months.
Incorporate SVG into the Mozilla trunk and add SMIL with support for mp3 and/or ogg vorbis. That'll be a real Flash killer.
That one wouldn't get very far, now would it...
You're on crack... what's the difference between emerge and apt-get from a security standpoint? In both you don't actually inspect the code before it's installed on your machine. You have to trust the repository admin for both systems.
Gentoo is really cool for producing systems optimized exactly for your system, making sure you have the official version of programs, and knowing that a package will be linked against the correct minor version of libraries. What it doesn't do is inspect the sourcecode for you.
My post was actually related to the Speech the parent poster was referring to.
Yours was just innane.
All of the vulnerabilities I listed made it into official releases before being patched. The bug this story is about didn't make it one day in the source tree, let alone into an official release.
Sorry about the Protegrity one, I must've linked the wrong one. I was looking for this one (the one exploited by the slammer worm).
You might want to check that gcc binary you're compiling gcc with to compile the kernel...
The "backdoor" that someone attempted to submit was a local privilege elevation bug, not a remote compromise.
Backdoor to windows not due until Longhorn ? ?
A sparse matrix takes up a lot less memory.