JavaScript for Line of Business Applications

A diabolical herd of pigs stole all of the front-end architecture from an innocent flock of birds and now they want it back! A team of special agent hero birds will attack those despicable pigs until they recover what is rightfully theirs, front-end JavaScript architecture!

Over the course of the next several weeks you'll be introduced to the following team of super hero birds...

The Red bird attacks with the force of their trusty IIFE, the basic block of all privacy.

Presentation explaining asp.net MVC4 including what's new, explaining how it works and finally implementing a real world application.

Like most other JavaScript developers, we’ve been in a callback hell. Functional Reactive Programming (FRP) is one, and in our opinion rather powerful, tool to improve the structure of your web app. This blog post introduces FRP concepts and benefits with Bacon.js, an FRP library for both browsers and server-side JS.

We’re very excited to announce the release of a massive new update to our Javascript client library. The new release adds a smarter connection strategy with additional fallback mechanisms such as HTTP-based transport. These changes further improve our support for legacy devices and network complications such as corporate firewalls.

The Javascript client library is our most widely used library. Its aim is to quickly and reliably connect browser based clients to Pusher. Connectivity is a very fundamental aspect of our service and we’ve put a lot of thought into making it the most comprehensive and considered connection manager available.

There's a lot of talk of various client-side kind-of-mvc libraries. Three of the popular ones I've used are Knockout, Backbone and Angular. 

While there are other comparisons of the three, I feel many of them don’t really touch on some of the aspects that I’ve come to learn from my experiences with the three.

First off, some observations of the individual librarie

JavaScript patterns and antipatterns collection

The advantages of Node.js for writing massively scalable servers are manifold. I’d like to share with you the advantages I think are most important: the ease of which you can write asynchronous server logic, the ability to write easily scalable servers, and the ability to write your app 100% in JavaScript.

Let's try to answer some questions: What is WebKit? What isn't WebKit? How is WebKit used by WebKit-based browsers? Why are all WebKits not the same?

Since Flowdock is all about real-time messaging, our web app posts and receives messages via a Socket.io backend. To support saving messages through Socket.io instead of a REST API, we wrote a custom Backbone.sync method. We also use Bacon.js a lot to manage message streams in the client.

As I was learning how to design and execute load tests, an experienced load tester told me the one rule you needed to be able to judge the effectiveness of a test execution: If something didn’t go wrong with some part of the application and/or infrastructure during the test, there was likely something wrong with the test you ran.

Editor's note: Péter Halácsy is co-founder and CTO of Prezi.

Startups identify with JavaScript. When you're just starting out, you need to be dynamic. You need to be flexible.