 Your new post is loading...
Your new post is loading...
Scoop.it!
A step by step guide on how we made our main Dashboard app 10x faster. Since node.js is perfectly suited to running multiple asynchronous functions in parallel, and since a lot of these internal API requests didn’t depend on each other, it made sense to parallelize them — fire off all the requests at once and then continue once they’ve all completed. We achieved this with the aid of the (incredibly useful) async module 
No comment yet.
Sign up to comment
Scoop.it!
A tiny foundation for creating reactive components with interpolation, data-binding, and plugins. It's simple, flexible and easy to extend. It aims to have a similar API to Reactive, but allow composition of views, like React. The major difference for other view libraries is that there are no globals used at all. Each view has its own set of bindings and plugins. This makes composition of views really easy.
Scoop.it!
From
ele
Ele (call it “Ellie”) is a streamlined environment for exploring, experimenting with, and sharing reusable custom HTML elements made with Web Components.
Scoop.it!
In this post I will demonstrate how to create a Treeview component using React and Flux. The React part is relatively simple and consists of two components; TreeView and TreeNode. It's worth noting that the TreeNode component is recursive in order to support n levels of nodes.
Scoop.it!
Matreshka is a framework for massive and endlessly extending single page applications (within the Universe, of course), written in JavaScript. It allows you to build the program architecture so that neither your team nor you can get confused in plentiful entities, logic described in HTML files, numerous restrictions of other frameworks and incomprehensible abstractions. Two-way data binding is implemented by bindNode method only and it does not require to change HTML, adding weird {{syntactic.constructions}}. Having set a few rules, a programmer can continue to work with data and forget about the state of the visible part of the application.
Scoop.it!
Aurelia employs several strategies when observing object properties. The best strategy is chosen depending on the features of the browser and the type of object/property being observed. Here's a run-down of the techniques used, in order of priority.
Scoop.it!
This is a hands on tutorial on Emberjs. We will be covering most of the Ember concepts, so that you can start building Ambitious web apps. The app which we are going to build is an Online Pizza Store. We will be working with various aspects of Ember in bringing this project to life.
Scoop.it!
Join us as we take an in-depth look at Facebook's React and how its core principles of components and one-way data binding can greatly simplify your client-side apps. We'll explore some example apps built in Salesforce and even look at how LevelEleven uses React to power some incredibly complex interfaces in its own products.
Scoop.it!
In some cases you might be able to avoid this problem by using paging or infinite scrolling, but sometimes that's just not good enough. For example, lists that are displaying only a few items at a time (like any kind of a log) would simply be very impractical from the users point of view. Another reason - you might be using libraries like SlyJS that load a whole list at once to calculate the size of the embedded scrollbar and to make list swiping and elastic bounds work properly. Ooooor - your client simply demands it. :)
Scoop.it!
![A Baseline for Front-End [JS] Developers: 2015 | JavaScript for Line of Business Applications | Scoop.it](https://img.scoop.it/W0EYRFAv7qpjXJe8UQbjTDl72eJkfbmt4t8yenImKBVvK0kTmF0xjctABnaLJIm9)
It’s been almost three years since I wrote A Baseline for Front-End Developers, probably my most popular post ever. It’s 2015. I want to write an update, but as I sit down to do just that, I realize a couple of things. One, it’s arguably not fair to call this stuff a “baseline” – if you thought that about the original post, you’ll find it doubly true for this one. One could argue we should consider the good-enough-to-get-a-job skills to be the “baseline.” But there are a whole lot of front-end jobs to choose from, and getting one doesn’t establish much of a baseline.
Scoop.it!
This essay explains how Git works. It assumes you understand Git well enough to use it to version control your projects. The essay focuses on the graph structure that underpins Git and how the properties of this graph dictate Git’s behavior. This focus on fundamentals lets you build your mental model on the truth, rather than on hypotheses constructed from evidence gathered while experimenting with the API. This truer model gives you a better understanding of what Git has done, what it is doing, and what it will do.
Scoop.it!
By building ang-news, you will learn how to develop CRUD (create, read, update, delete) services, securely authenticate users, access servers with $http, communicate with REST APIs using $resource, enable three-way data binding with your server, create directives for your user interface and more. Once you have finished building the ang-news application, your users will be able to:
Scoop.it!
Mobile development is a complex business, with multiple platforms (iOS, Android, Windows) and many more frameworks (Titanium, Xamarin, and a bucketload of HTML5!). I am firmly of the opinion that there is no silver-bullet, no one framework that is right for everyone. For that reason, this article is split into two sections, the first discussed the pros and cons of React Native, and the second discussing how it affects the various communities (e.g. native iOS devs, Xamarin devs etc …)
|
Scoop.it!
We’ve been running Node in production for a little over two years now, scaling from a trickle of 30 requests per second up to thousands today. We’ve been hit with almost every kind of weird request pattern under the sun. First there was the customer who liked to batch their data into a single dump every Friday night (getting called on a Friday night used to be a good thing). Then the user who sent us their visitor’s entire social graph with every request. And finally an early customer who hit us with a while(true) send(data) loop and caused a minor emergency. By now, our ops team has seen the good, the bad, and the ugly of Node. Here’s what we’ve learned.
Scoop.it!
There are a lot of new fancy web applications out there that are using real-time functionality. You can see examples of this used to great effect in Google Docs' multi-user editing, and the way all the social media sites update you of whats happening in real time. All of these applications are a far-cry from the old "request-response" pages of the early 90s, in fact the only way to achieve realtime web communication back then was to use Java Applets, and I believe you could use Flash for it too. Luckily I'm not 8 years old in 2015, and today we have Web Sockets that allow us to maintian persistent connections between client and server!
Scoop.it!
From
github
knockout-react - A wrapper / bridge for using React.js with Knockout and Knockout with React.js
Scoop.it!
There seems to be a community forming behind Aurelia, so I figured I'd give it a try and build something of manageable complexity. I landed on a treeview component since it requires me to touch upon several of the different binding types in addition to recursive templates. The treeview supports recursive rendering of a few U.S. states with cities and boroughs. There is also support for expand/collapse of nodes with children. Aurelia is a modern framework, with support for ES6 out of the box, which requires some setup to get transpiling and the rest of the development environment up and running. In order to simplify the process I recommend downloading the provided skeleton project and use it as a baseline. Aurelia is still a new framework, but the documentation on their website is already impressive and answered most of my questions.
Scoop.it!
Users notice if sites and apps don't run well, so optimizing rendering performance is crucia! To write performant sites and apps you need to understand how HTML, JavaScript and CSS is handled by the browser, and ensure that the code you write (and the other 3rd party code you include) runs as efficiently as possible.
Scoop.it!
In this blog post I’ll share my first impressions of the framework and I’ll try to keep them as less subjective as possible, although my affinity to AngularJS. I’ll start with the general changes and after that keep going into details. It seems it got modern for the JavaScript MVW frameworks to drop controllers from their components (starting from Backbone.js). Instead of using controllers, AngularJS 2.0 bet on component-based UI, similar to ReactJS. The core team dropped controllers but added three different types of directives:
Scoop.it!
ES6 generators seem to be a very good fit for handling asynchronous actions. I've been using a library, generator-runner, which uses ES6 generators for running async tasks. To use the library you create a runner that takes two parameters:
Scoop.it!
How do React components work? How do you build an application of nothing but React components? Chris Bland shares best practices he's learned when building with React.
Scoop.it!
The virtual DOM is one of the key characteristics of React. When you render a component, React creates a lightweight description of the UI, diffs it with the previous version, and generates a minimal set of changes to apply to the DOM. That diffing algorithm is very fast, making React particularly well suited for apps with a lot of UI changes. That prompted me to revisit a type of application I’ve built in the past with different languages and frameworks: a trader desktop showing real time market data updates. This new version uses React for the client-side and Socket.io to push simulated market data updates to the client.
Scoop.it!
Have burning questions about AngularJS 2.0? Want to know what we're up to, what's planned or get a status update? This is the place. In this talk we'll start by looking at the fundamental motivators and design goals of AngularJS 2.0. Next, we'll talk about specific features such as Dependency Injection, Templating, Binding and Routing. You'll gain a solid understanding of what AngularJS 2.0 comprises and have a feel for what the next generation of JS client development will be like.
Scoop.it!
The tips and tricks of using protractor for writing e2e tests with AngularJS
Scoop.it!
From
medium
Before I get into the nuts and bolts of our process, it’s important to chat about why Ember is better for design iteration (at least in an agency setting) than most other javascript frameworks & libraries. This is not about data immutability or render speeds. This is about running a better business through a deeper understanding of technology. Things like React, Flux, Backbone and jQuery (amongst many others) fall into the category of “progressive enhancement”. They’re libraries that bolt on to a server rendered template, and allow it to do things it couldn’t do before. On the surface, this seems great — you add bit and bobs to the good old browser environment, and only use what you need. However, as an ambitious project matures, so does the UI, and it’s requirements. So you reach out and grab another library that does another thing, and then write some ~simple~ code to make library X work nicely with library Y. Progressive Enhancement sucks when there’s churn in the project’s maintainers.
|
