Many of the techniques Schmidt explores in this month’s feature are present in the initial version of Windows 8 and WinJS, but Schmidt says many developers are unclear on how the techniques work and relate to each other. He wrote this month’s article with the idea of explaining “how the entire package of error-handling works together from a top-down, holistic perspective.”
The latest version of WinJS and its attendant tooling deliver what Schmidt describes as “ready to go” templates and controls that help streamline development. The updates also deliver significant performance improvements and streamlined WinJS app development.
Speaking of performance improvements, next month Schmidt will publish a follow-on article focused specifically on performance issues. What advice does he have for developers struggling to ensure that their WinJS applications are performant?
“The No. 1 thing I’d recommend is to really use the platform. Any retained-mode system—whether it’s HTML or XAML or PDF or you name it—has certain sets of capabilities that are natively implemented and highly optimized within it. In as much as your app code and script calls into and leverages those capabilities, the better performance you’ll get,” Schmidt says. He adds that the latest version of WinJS pushes more of the features lower down into the implementation, where they can be optimized for best performance.
Are you working with WinJS? If so, I’d love to hear about your experience. E-mail me at firstname.lastname@example.org.
Michael Desmond is the Editor-in-Chief of MSDN Magazine
More MSDN Magazine Blog entries >
Browse All MSDN Magazines
Subscribe to MSDN Flash newsletter
Receive the MSDN Flash e-mail newsletter every other week, with news and information personalized to your interests and areas of focus.