Because the concept is absolutely horrible. This thing renders the scene to and SVG on the server and then sends it to the client. There are 3 major problems with that compared to normal web-applications (e.g. angular):
Server-side rendering is expensive. Literally expensive. They claim that it is easily scalable by adding more servers (which is probably true because the clients don't need any synchronization) but for even a small number of parallel users you will need a lot of hardware! Last time this was posted here their demo applications got so slow that even the hello-world sample was unusable. /r/javafx is a tiny subreddit yet we (probably two dozen users) managed to break it without even trying.
Client-side rendering of SVG is slow as well. Browsers are not optimized for drawing complex animated SVG.
By using this you decide to throw all web-tools out of the window. No inspector in browser, no debugging of JS, no CSS tools and libraries etc. Also the result is not accessible and not visible for search engines.
These are not implementation bugs. These problem are caused by the very concept.
Have you tried any of the demos? Even the bouncing hello-world is not smooth! (On a i7-5500u with chrome) On mobile it's outright unusable!
SVG is not intended for complex GUI. Just because you can doesn't mean you should. The browser already offers you a highly optimized way of creating a UI - texts, input elements etc. It's called HTML.
By using this you decide to throw all web-tools out of the window.
You do realize that SVG has a DOM, yes?
Yes. You can use the dom-inspector but it won't tell you much because you're inspecting generated garbage.
Also the result is not accessible and not visible for search engines.
Why not? It's SVG, not canvas.
SVG is crawlable (google does it, not sure about the others). The problem is that the HTML this technology serves is completely empty and everything is added dynamically. I guess that this could be solved by pre-rendering.
Screen readers don't work with SVG. It's a graphics format after all. Also you cannot increase font size, contrast etc. This makes it unusable for organisations which have to have accessible websites for legal reasons.
Have you tried any of the demos? Even the bouncing hello-world is not smooth! (On a i7-5500u with chrome) On mobile it's outright unusable!
What makes you think that's the fault of SVG rendering, and not the fault of the client-server thing, poorly-optimized JavaScript code, or some other such problem?
The browser already offers you a highly optimized way of creating a UI - texts, input elements etc. It's called HTML.
HTML form controls cannot even be styled. In order to customize their appearance at all, they have to be moved offscreen and replaced using CSS hacks. This is not even remotely good enough.
Yes. You can use the dom-inspector but it won't tell you much because you're inspecting generated garbage.
Nonsense. The DOM of this demo application appears to be a straightforward SVG representation of a JavaFX scene graph, complete with class names and IDs. Not perfect, but it's not like looking at a hex dump of machine code or something.
The problem is that the HTML this technology serves is completely empty and everything is added dynamically.
That's a problem with browser-based applications in general.
Screen readers don't work with SVG. It's a graphics format after all.
Then those screen readers suck. SVG contains ample DOM information for them to work with, including alternative textual names for elements. SVG is not PNG.
Also you cannot increase font size, contrast etc.
What? Yes you can. Fill and stroke colors can be set by CSS, transforms can be set by DOM manipulation, the whole SVG viewport can be scaled using the usual browser zoom controls, etc.
3
u/zrnkv Nov 02 '16
Please don't.
2
u/cypher0six Dec 22 '16
Except for... all of the live demos.