Applications built with web technologies, something that was a curiosity a few short years ago, have emerged onto the scene as a must have for most organizations. Transcending websites and providing users with a more open and unbounded experience, web applications are everywhere. Likely the main reason you are reading this series is to determine how modern frameworks enable you to build web applications.
The assumptions made often turn out to be wrong. What’s worse is that these choices may prove to be correct for a very long time before coming back to bite us. During this period of blissful ignorance, toolkits can become tremendously popular and become a vital part of large, complex codebases.
We have previously discussed the look and feel of web frameworks. While we often become interested in a framework based on the stylishness of the widgets and applications it can create, this may lead to a similar approach to how we have historically selected music. Traditionally, you would go out, buy an album, maybe from a band you knew, with a great album cover and a list of interesting tracks.
Perhaps the album was currently #1 in its popularity on the Billboard charts? Maybe you even sample a few tracks while in the music shop. However, once you got home with your CD and played it over your kick-butt, valve amplified, highly optimized sound system, you find out that it was mixed by someone who thought that no one listening on an MP3 player through cheap headphones would ever notice the low sample rate and removal of the bass! Instead of feeling like you are in the middle of a concert, you feel like you are listening to a band playing in a toilet over a phone. So the album was optimized for its look and feel while ignoring the foundational architecture needed to create an album that scales under the demands of a highly optimized stereo system!
While instruments such as guitar and drums are part of a band, how they are used by the musicians define the style of the band’s music. Similarly, the elements of an application user interface connected together define the user experience. In this post as part of our ongoing series about frameworks, we are going to explore in depth the ways in which frameworks enable an overall UX design.
Whether it is Top 40 or classical or R&B, artists and music have a recognizable look and feel. When looking at frameworks, some simply provide us with a bag of instruments, while others provide us with chord progressions and album covers we can customize.
Probably the most common question we get asked as we get to know an organization is “What framework should I use?” No matter what some people would have you believe there is no straightforward answer. The answer though is founded in our typical response of “What are you trying to do?”
For a concise read on why the enterprise should care about using TypeScript in its applications, look no further than Remo Jansen of the Aon Centre for Innovation and Analytics’ presentation on the 6 reasons you should be using TypeScript.
The SitePen engineering team has been using TypeScript since it came onto the open source scene 5 years ago. We’ve built several customer applications using TypeScript and TypeScript frameworks. Our next generation version of Dojo (which will be the defacto enterprise framework for organizations who value sustainability, longevity and true open source software) is 100% TypeScript.
With a healthy respect for what the TypeScript team has accomplished and being enthusiastic contributors to the TypeScript language through development, our TypeDoc improvements and our testing framework, Intern (built with and for use in testing TypeScript), we are well-positioned to modernize applications beginning with tech stack migration, forward-thinking architecture, TypeScript development, team training and commercial support.
While we’ve been offering online TypeScript workshops for quite some time, our UK contingent of engineers have their hearts set on delivering a public training course to the London (and surrounding countries) developer community. So, for one time only, please join our CTO, Kitson Kelly – a team-labeled TypeScript purist – as he brings you some serious TypeScript training and to the next level in enterprise web development.
August 31, 2017 | 9:00 – 17:00 BST
Location: TBD, London
- Introduction to TypeScript: Benefits and key TypeScript concepts
- Compatibility with ES6+: Which ES6 and later features are supported
- Development Environment Setup: Quick and optimal environment setup
- Basic types: Working with types
- The power of interfaces: Leveraging TypeScript interfaces to improve code readability
- Extending interfaces: Unions, aliases, and other advanced interface features
- Classes and composition: Using Classes, functional composition, and differences from ES Classes
- Generics: How to use generic types for building APIs
- Ambient Declarations: Leveraging other type definitions
- Decorators and Metadata: Syntax for efficient extension of Classes and other language features
- Advanced TypeScript configuration: Additional options for getting the most from TypeScript
- Testing: A robust testing workflow with TypeScript
- Debugging: Troubleshooting and finding errors in your application
- Future of TypeScript: Summary of highly anticipated TypeScript features
Early Bird pricing is now available!
Can’t Attend/Still Need Help with Typescript?
TypeScript 2.3 is the latest version in the quarterly release cycle from the TypeScript team. This release contains several useful additions to TypeScript which we have already started to leverage within some of our current projects. Let’s take a closer look!