Its inpredictable, buggy, slow. Yes it has nice fontrendering, have to give it that.
-
-
Prikaži ovu nit
-
What it took for me to figure it out is building code-editors. Anything out of the primary usecase-flow of HTML and you learn its a very domain specific renderstack.
Prikaži ovu nit -
If you look at a basic JS UI from a systems point of view the 'total system complexity' becomes absurd. Megabytes of JS on top of a JS engine on top of a 'nobody knows how it works' CSS engine and render engine. Thats a LOT for a todolist or a button.
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
-
-
The rationale is usually that nobody wants to deal with UIs, so why not offload the whole thing to web designers, as there are plenty of them around (same reason why Scaleform was so popular, being a Flash engine).
-
I have to say, even as someone that builds them, UI is its own special type of hell regardless of backend. But HTML makes it so infuriating to do things 'right' especially when it gets complex i just can't anymore.
- Još 1 odgovor
Novi razgovor -
-
-
DOM-based render takes a long time (>50ms); with 120Hz screen, AR around the corner, it won't be good enough. It needs to have its "asmhtml", like wasm did for js.
-
Maybe, i'm not even talking about perf though. Its also simply the API itself i strongly dislike for UI.
Kraj razgovora
Novi razgovor -
-
-
I think the driver in the webtech nightmare is the need to have many mid-level collaborators tackling huge projects which must be done in much less than eight years. The problem space is in breadth not height. I may be totally off topic ;-)
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.