The Acid tests test for correct behaviour even with broken standards - so they deliberately include non-standard JS, CSS and HTML to check that the browser handles the non-standard data according in the way specified in the standards.
But it's unfortunate that the preferred Ruby AJAX design pattern still includes prototype.js,
because that library as written is fundamentally dangerous. It's written in a fashion which
demonstrates that the author is very adept with JavaScript and functional programming in general;
but it also does some unpardonably cute tricks in extending core objects, thereby changing the
overall JavaScript environment and making the core AJAX library not play nicely with others. (And
if ever there was an environment where you need to have good manners and not piss in the pool,
it's the browser + JavaScript environment.)
Agreed. So do others: check out http://www.mochikit.com/ for a js library that doesn't piss in the pool.
> Images can't be read by external devices for accessibility purposes.
Again, true, flash wins in this case, although its not easy I suspect. Are there accesibility tools to render flash as html or similar?
However in the case above, accessibility is well catered for as if images are not supported, the plain html is used, which is exactly the same content as for with images.
My point was that this uses flash, which is not great, I'd prefer to use images. It also involves a lot of extra markup to the html, which is not necessary with the above method. However I agree it's a hack until svg fonts or similar are available.
The above works better IMO as it uses plain old images to do the job (I dislike flash), plus the markup does need to inlcude these messy tags - it just uses the element text.
e.g.
<h1>Some Heading</h1> is auto-replaced by <h1><img href="generated_url.png"/></h1>
where the generated img contains the text "Some Heading" in whatever font you use.
ok, so there's a performance hit, but images are cached, so its only for the first viewing. The real beauty of it is you just have to chance the text and not worry about the font! Magic
Also the technological challenges were significant, with no real solutions to the problem of large scale resource allocation. I've heard them talk of a 'magic number' of machines they could manage (3000? - they were closed mouthed about it) before the system was unworkable. They're vision was for 50,000, but they were mostly focused on a economically inspired centralised managment system, which wasn't gonna scale, IMHO. The technology behind 'Utility computing' (HP) (or 'Autonomic computing' (IBM) or 'grid computing' (academia)) is not developed enough IMO to be solid and cost effective at the moment. Give it 5 years.
(disclaimer - this is the focus of my PhD)
Agreed, it is designed more with security in maind the IPv4 was. Also many other improvments, such as priority routing (for streams) and much improved multicasting.
I think the shortage issue is an overplayed and dubious card. There is way more to IPv6 than that. Its about making the internet 'smarter' as well.
--Jaques
Slashdot Mirror
The Acid tests test for correct behaviour even with broken standards - so they deliberately include non-standard JS, CSS and HTML to check that the browser handles the non-standard data according in the way specified in the standards.
Hence why they don't pass validation tests.
This immediately reminded me of Genly Ai and Estraven's epic trip across the ice field of Gethen. Damnit, I really liked that book :)
> Images don't resize with the browser.
Flash doesn't either, AFAIK. Quick test confirms.
> Images can't be selected and pasted as text.
True, but again neither can flash.
> Images can't be read by external devices for accessibility purposes.
Again, true, flash wins in this case, although its not easy I suspect. Are there accesibility tools to render flash as html or similar?
However in the case above, accessibility is well catered for as if images are not supported, the plain html is used, which is exactly the same content as for with images.
My point was that this uses flash, which is not great, I'd prefer to use images. It also involves a lot of extra markup to the html, which is not necessary with the above method. However I agree it's a hack until svg fonts or similar are available.
The above works better IMO as it uses plain old images to do the job (I dislike flash), plus the markup does need to inlcude these messy tags - it just uses the element text.
e.g.
where the generated img contains the text "Some Heading" in whatever font you use.ok, so there's a performance hit, but images are cached, so its only for the first viewing. The real beauty of it is you just have to chance the text and not worry about the font! Magic
Also the technological challenges were significant, with no real solutions to the problem of large scale resource allocation. I've heard them talk of a 'magic number' of machines they could manage (3000? - they were closed mouthed about it) before the system was unworkable. They're vision was for 50,000, but they were mostly focused on a economically inspired centralised managment system, which wasn't gonna scale, IMHO. The technology behind 'Utility computing' (HP) (or 'Autonomic computing' (IBM) or 'grid computing' (academia)) is not developed enough IMO to be solid and cost effective at the moment. Give it 5 years. (disclaimer - this is the focus of my PhD)
Agreed, it is designed more with security in maind the IPv4 was. Also many other improvments, such as priority routing (for streams) and much improved multicasting. I think the shortage issue is an overplayed and dubious card. There is way more to IPv6 than that. Its about making the internet 'smarter' as well. --Jaques