DoneJS 3.0 is out! 🎆
Loading
A Fortune 100 company who needed to ensure millions of users are never without service wanted to streamline their DevOps procedures to solve a myriad of problems most enterprise-level companies face when working at a large scale. In particular, they were interested in:
- Alleviating some of the burdens of Site Reliability Engineers (SREs)
- Minimizing the risks of human error
- Ensuring proper communication and visibility around issues when they arose in a way that could scale efficiently as the infrastructure grows.
Let’s investigate these problems in-depth and see how DevOps automation with StackStorm helped SREs automate common tasks, minimize downtime, and sleep easier in a scalable, reliable, and fully customizable way.
Mick McGrath
{% raw %}
Earlier last month CanJS 4.0 was released bringing a load of new features. We heard early (while 4.0 was still in prerelease, in fact), that DoneJS users wanted to upgrade. Once 4.0 was out we had to answer a tough question: do we wait on a new breaking StealJS release, add other features, or release a DoneJS 2.0 right away?
The Bitovi Team
{% raw %}
If you are brand new to CanJS, we suggest reading its technology overview for background information on what CanJS does and how it works.
Dear JavaScript Community,
The humble DoneJS core team is proud to present CanJS 4.0. Like previous major releases, it represents a unique enrichment of CanJS's vision. Where 3.0 was about making your app more stable and less affected by rapid technology changes, 4.0 is about simplifying CanJS and enhancing your understanding of your application.
So turn on your terminal, clean off your keyboard, boot up your browser, alt-command-I (⌥ ⌘I ) your console, and get ready for some fun as we walk through the most important improvements in CanJS 4.0!
Justin Meyer
CanJS, for better or worse, allows a near endless variety of design choices. If you like MVC, MVVM, centralized state management, etc, you can build your app that way.
Enabling this level of flexibility is difficult, especially because we don’t know what sorts of things people might want to integrate into CanJS.
Justin Meyer