Ember.js provides an MVC application framework for creating rich client-side apps. But Ember.js doesn’t control the Web’s infrastructure; on the contrary, it depends on them. The Web consists of many different technologies, each of which is run by a different committee or group. How can Ember.js create a stable, useful framework when Web standards are constantly changing, and run by different groups? In this talk, Matthew Beale describes the different standards bodies, how they work, and how Ember tries to push forward with development while taking the rest of the Web, and its standards, into account.
So, we work with technology. Technology is fun, interesting, and provides many of us with intellectual challenges and careers. But technology is about people, not just computers. In this talk, Tim O’Reilly talks about the people who use technology, and how we should think about them. We should think about empathy and communication, at least as much as we think about lines of code. What are we contributing to the world — not just in code, but to our fellow humans, and to the society in which we live? If you work with technology, consider this short talk, which will hopefully inspire us to remember the people behind the technology, and the reasons why people use the products we make.
It’s increasingly common to use a client-side framework to create rich Web applications. But what happens if you already have some client-side code, and want to migrate (slowly and carefully) toward using a client-side framework, such as Ember.js? In this talk, Brandon Hays demonstrates how you can migrate existing JavaScript code to a framework, so that you can stop managing the DOM directly, and think in terms of high-level JavaScript (and Ember) objects.
Client-side JavaScript frameworks are increasingly popular, and even necessary, for modern Web applications. But how can you decide from among them? What are the differences between the leading frameworks, and how do they approach the same task? In this talk, Craig McKeachie describes and discusses several popular frameworks, including Ember.js and Angular.js.
Ember.js is a leading client-side framework — letting you create rich, desktop-style applications that run within the browser, and which communicate easily with a server. In this talk, Yehuda Katz describes what the Ember.js developers have aimed to do, and their process for doing so. How have they released new versions without breaking previous code? How have they tried to learn from other frameworks? This talk shows how Ember.js has tried to do all of these, and more, as they build a solid framework that is growing in popularity.
MVC (model-view-controller) is a well-known paradigm for designing applications. Ruby on Rails was one of the first Web frameworks to use MVC, basically forcing us to use MVC in order to create a Web application. MVC works great at first, but does it work over time? As our applications grow in size and complexity, does MVC still make sense? In this talk, Peter Harkins describes the sorts of problems that MVC-based applications can encounter as they grow and age — and the types of solutions that you can apply to your code, in order to make it work better, and become easier to maintain.
Jython is a version of Python that runs on the JVM. The Jython project recently celebrated release 2.7, which is compatible with Python 2.7. What are the aims of the Jython project, and who uses it? What obstacles did the Jython developers have to deal with on the way to this release? And what new features does the new version include? In this talk, Jython committer Jim Baker helps to answer these questions, describing how Jython is good for the Python and Java development communities.
Docker provides you with containers, which are sort of (but not quite) virtual machines. Why has Docker become so exciting in such a short period of time? What can you do with it? In this talk by Brian Goff, we learn what Docker is — and also what it can do for you, beyond what you might expect. If you’re new to Docker, or curious to know how it can help to improve your development or deployment, this talk should be of interest.
Craigslist is one of the best-known, and most popular, Web sites, allowing people to find household items, find apartments, and jobs (among other things). How does Craiglist’s back end work? How is it able to provide such fast and responsive search results? In this talk, Jeremy Zawodny describes how Craigslist has evolved over time, and how this evolution has allowed them to improve their search responsiveness. If you’re interested in how to scale Web applications, then Craigslist is a great example, and their technology choices are useful to learn about, too.
How do you debug your Python programs? There are a variety of techniques, but even the strongest advocates of using “print” statements eventually need to use a debugger. In this talk, Matt Boehm demonstrates why and when you want to use a debugger — and the variety of debuggers that exist within the Python world.