HTML: <!DOCTYPE html> Native: int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPCTSTR lpCmdLine, int nCmdShow)
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Because we love UIView
-
Cocoa Touch is definitely nicer. What weirds me out is the nostalgia for Win32.
End of conversation
New conversation -
-
-
A core tenant of Graphistry is that targeting parity with "native" frameworks is undershooting what tech can do by 100X+, so I tend to tune out those folks already ;-)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I'd love a lightweight dom (drop a bunch of older API and model, drop a lot of css and js older stuff). I kinda miss css&dom when I work elsewhere. I also miss devtools. A lot.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
They give better results, they're not necessarily nicer to use.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It seems interesting whether people would hold this same opinion if accessing DOM would be as fast as calling functions in the same language (e.g., without costs of JS<->C++ FFI).
-
In practice the main cost with accessing the DOM is when you modify it and the engine has to resolve Layout and Paint for most of the page. Or when you do a bunch of staggered small or big changes.
End of conversation
New conversation -
-
-
I think a lot of it has to do with very painful lingering memories of "X feature of the DOM sorta only semi half works on IE, sometimes, during certain phases of the moon on alternate Tuesdays." Compared to that, anything seems good.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.