4 ms·
You're totally right, if a page is merely serving static content with hyperlinks between the pages. For many types of pages, however, that's not the goal, and u
by zeugmasyllepsis 9y ago
You're totally right, if a page is merely serving static content with hyperlinks between the pages. For many types of pages, however, that's not the goal, and using JavaScript makes sense. Think of an interactive data visualization, where nearly the entirety of the content depends on dynamic user input controlling aspects like filtering and highlighting.
There are many cases where developers use JavaScript when plain CSS and HTML would do, but there are also many pages that simply do not fit that simple model. And between those two extremes is a large space of application with a mixture of static content and interactivity. Don't focus on a single usecase and ignore the rest.
- moron4hire 9y agoAs someone building a business off of VR in the browser, I think we should always have a fallback. The systems we use for building the web--whatever they may be--should do more to encourage accessibility, rather than leave it as an "exercise for the reader", aka "afterthought". Users of these systems have a legal responsibility to make their site accessible. As framework developers, I think that we must share that responsibility, at some level.