We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Architecting large Single Page Applications with Knockout.js

Formale Metadaten

Titel
Architecting large Single Page Applications with Knockout.js
Serientitel
Anzahl der Teile
170
Autor
Lizenz
CC-Namensnennung - keine kommerzielle Nutzung - Weitergabe unter gleichen Bedingungen 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
These days it's easy to get started building a Single Page Application (SPA). Dozens of frameworks are clamouring to pitch their trivial "hello world" and "todo list" examples. But the moment you step outside the predefined path and begin actually crafting something for a real business, you face an explosion of choices. This talk is about experiences of building large SPAs and maintaining them over time. In part, I'll demonstrate pros and cons of various technology choices, such as TypeScript, Grunt, and AMD module optimisers. In part, I'll demonstrate some Knockout.js-specific techniques, such as the new and powerful "components" feature that improves maintenance, testability, and runtime performance. Throughout, I'll share lessons learned from building and maintaining the core of the Windows Azure management portal, an exceptionally large and high-profile SPA whose various parts are developed by many different teams within Microsoft. I hope these experiences will prove useful when you build your next rich JavaScript application.