Your current filters are…
CommonJS is a community-driven effort by volunteers with diverse backgrounds and interests to converge on a minimal common ground that is sound and scalable. The goal is to make writing portable JavaScript applications that run on servers, browsers, desktop applications, and secure sandboxes not only possible, but also accessible to developers and development tools without vendor lock-in or steep learning curves.
Christoph will attempt to paint us a picture of where CommonJS is today and where it is headed. CommonJS is well on its way to realizing the dream of portable JavaScript applications composed of libraries from all over the Internet. That is, modular JavaScript that runs everywhere.
by Joe McCann
The programming language that was once only associated with “script kiddies” and annoying popups on websites is now a first-class citizen amongst other languages. JavaScript is no longer simply used for DOM scripting or even Ajax-ified web applications, like Google Maps, but it is being used in far more innovative and productive ways.
Joe’s presentation will walk us through the current state of JavaScript programming and the various endpoints for the language: From the standard desktop web client (the web browser) to the server, mobile applications, desktop applications, and beyond. His talk will showcase the true capabilities of the language as an end-to-end solution for business and personal usage.
We all know that modules are in our future. ECMAScript.Next modules (aka "Harmony" modules) will start appearing in browsers in early 2012. Too bad Harmony modules won't be universal 2021 when IE9 will finally be dead.
No need to wait! AMD and CommonJS Modules/1.1 are fully supported in a wide variety of environments already. But why are there two standards? Which one should I pick?
We'll take a quick look at each of the formats, compare and contrast their features, discuss the benefits of using modules now, and finally draw some conclusions.
Node.js has brought the JavaScript event loop from the browser to the server by pairing it with a strictly non-blocking paradigm. This model has proven to work well for I/O centric server applications. If JavaScript is to become a true general-purpose programming language, there will be a need for alternative models of concurrency.
In this session, Hannes proposes an alternative concurrency model for JavaScript that is based on the Actor model. Starting with W3C Web Workers, he will demonstrate how to build a system that has the benefits of threading, such as true preemptive scheduling without the pitfalls of shared data locking.
Hannes will focus on features aimed towards highly concurrent CPU-heavy server-side applications, including selective data sharing, concurrent lock-free data structures, functional programming, and read-only data.
NoFlo is a JavaScript implementation of Flow-Based Programming, a way
of separating the control flow of software from the actual software
logic. It helps organizing large applications, and especially in
importing and modifying large data sets.
FBP itself is not a new idea, coming from 70s IBM concepts of more
manageable business workflows, but NoFlo refreshes these concepts and
brings them to Node.js applications.
The MIT-licensed NoFlo library can either be used to run full
flow-based applications, or as a library for making complex workflows
or asynchronous processes manageable.
This session will introduce Flow-Based Programming to the audience,
and show how NoFlo can be used for large-scale data processing. It
will also contain a bit on the lighter side of NoFlo: how to simplify
user interactions through it.
Node.js has captured the attention of early adopters by clearly differentiating itself as being asynchronous from the ground up. Now that server-side JavaScript is at the cutting edge of the asynchronous, real-time web, it is in a much better position to establish itself as the go-to language for synchronous CRUD webapps and gain a stronger foothold on the server.
Oleg’s talk will cover the current state of server-side JavaScript beyond Node by mapping out the key standards and technologies as well as their respective positions in the stack. He will introduce Common Node, a synchronous CommonJS compatibility layer using node-fibers, which bridges the gap between the different platforms. He will give us a tour of Common Node’s internals, compare its performance to that of other implementations, such as RingoJS, and go through some ideal use cases.
A case will be made for a cross-platform, synchronous, Rails-like framework. In conclusion, he will identify new areas where server-side JavaScript can really shine, including API mashups, collaborative development and crowdsourced functionality.
Wakanda may provide an all-in-one solution, but it’s far from being a monolithic platform! Sure, you get a development studio, an Ajax framework, an HTTP Server, an application engine, and a database, but it can very easily interact with your existing tools, frameworks, and libraries. Learn how, as a developer, you’ll be able to share your own widgets, modules, services, and plugins between your applications and externally with any compatible development community. Find out about the power of system workers and Wakanda’s datastore HTTP API to bring your own JavaScript tools to Wakanda Studio.
by glenlipka
Programmers often create an application’s user experience (UX) without involving designers. Learn how to optimize the UX by doing less work and by using client-side frameworks. Learn when to introduce new patterns and when to stick with existing ones.
Design is all about decisions. Programmers make decisions every day that will affect their product’s success. Even without being a designer, you can create a great user experience.