2 ms·
That's because usually there is a browser-based layer which runs that HTML/JavaScript. Here it is Metro UI (via HTML5) powered using JavaScript (running native
by photon137 14y ago
That's because usually there is a browser-based layer which runs that HTML/JavaScript.
Here it is Metro UI (via HTML5) powered using JavaScript (running natively on Windows) - equivalent to a C++ native app with a Metro UI.
- flatline3 14y agoI don't really understand why this provides a better environment for producing top-quality media applications over the platforms on the market today.
- photon137 14y agoIt doesn't - it provides a perfectly equivalent platform. In all cases, it will be the codecs registered with the OS that would be used - so the quality of the media cannot be better/worse. Where this differs is from a developer perspective - you don't have to learn a non-standard UI API (XAML/WinForms/MFC/COM/ATL/Qt/Gtk/Swing/awt/whatever) or a language you're not familiar with (C#/C++/Java - pick any). But you can be sure that the experience will be precisely the same - no API hacks to achieve something specific, nothing at all.
- flatline3 14y agoIt's perfectly equivalently poor. What makes those platform APIs useful are all the tools they provide to simplify the creation of great, well-performing UIs that exceed the user's expectations.
- photon137 14y agoWell, MS provides Visual Studio for this - which isn't a bad toolchain, in my opinion.