I was passing time before a doctor's appointment, and found an interesting article in American Scientist.http://www.americanscientist.org/issues/pub/pixels-or-perish
I'll summarize some disadvantage points I picked up:
1. Pixels: The problem of fractional pixels. SVG helps, with animations and responsive design...
2. Complexity. D3.js, Processing, R, etc. help but it still takes a good deal of technical skill to compose diagrams for the web.
3. Permanence - Will today's content exist on the web of tomorrow. A URI might change, be restricted, or cease to exist in the future. Specs might be deprecated. Researchers are gravitating to PDF for stablility, especially with vector graphics.
This had me thinking about:
- Declarative HTML and CSS rather than JSON and helper scripts.
- Scoped CSS in Content Tools (polyfill somehow?).
- Is anybody working with MDV for SVG?
- Can some interactions be declarative?
- Native JS events for Elements leaving the visible area and/or being removed (videos in a slideshow or in google reader).