Tag Archives: javascript

posted

June 28, 2018

Migrating from AngularJS to React

by

angular-react

Most organizations with a web application will inevitably need to make a decision regarding their current front-end framework.  I’ve personally been involved with two projects that have come to this crossroads. One of the two applications was written in AngularJS, the other in Backbone.js. In both cases, the organization decided that the best course of action was a full rewrite using React and Redux.  In the case of the AngularJS app, a gradual migration approach was considered and I was lucky enough to have the opportunity to investigate this possibility.

read on

posted

April 6, 2018

ForwardJS SF 2018 Recap

by

ForwardJS was the first developer conference that I ever attended, and it was a pleasure to be able to attend again this year. Forward has been releasing batches of the recorded talks on YouTube, so I thought that I would share a few of my favorite talks from this year’s conference, along with the video and slides when available.

read on

posted

September 28, 2016

Grio and Angular 2: Are They Ready for Each Other?

by

At Grio, we love Angular.  By my estimation we currently use it for at least half of our front-end web application code.  And I in particular have affection for it, so I greeted the recent release of Angular2 with some interest and trepidation.

The release was just an event, though. The framework had already been around long enough for me to fret about it for some time.

read on

posted

August 9, 2016

Introduction to React Native

by

React Native underlines a JavaScript framework used in writing real and natively rendering mobile applications for Android and iOS. The framework is based on React, which is Facebook’s JavaScript library used in building interfaces for web applications. Building a mobile application using javascript isn’t anything new. The similar technique has been used in frameworks such as Ionic, Sencha Touch, Phone Gap, Cordova, and the list goes on.

read on

posted

July 8, 2016

Intro to Elm

by

In this blog post I’ll be covering Elm, an up and coming functional programming language for building web application front ends. Elm compiles into JavaScript and utilizes virtual DOM technology to efficiently render web UIs. Elm focuses on simplicity for the developer with a helpful compiler and an easy to understand application architecture.

read on

posted

December 30, 2015

Prototyping with P5

by

When I wanted to create a proof of a concept project for one of the game ideas I had, I found many tools and gaming frameworks. However, most of them had a steep learning curve which required a significant time investment before the game could be played. Then I discovered P5, a Javascript library inspired by the Processing language, which made it very easy to get started.

read on

posted

August 13, 2015

Chrome Extension Basics

by

I use Chrome extensions all the time and decided it was time to figure out how to make my own.  I found it to be incredibly easy and I’d like to share with you some of the basics, as well as an example of an extension I made.  Let’s get started!

read on

posted

February 1, 2015

Meteor

by

For the past year, I’ve been working mainly with AngularJS and before that Ruby on Rails. I’ve never heard of Meteor until a few weeks ago. I am intrigued by the idea of tightly connecting the client and server together in a synergistic manner that allows for fast responsiveness, which is what Meteor is all about. I decided to go through Meteor’s tutorial online and get a feel for why the framework differentiates itself from other current technologies. From a very high level perspective, Meteor is a very good solution for quickly building an application from the ground up and provides some cool features out of the box.

read on

posted

January 21, 2015

Frontend Resolutions for 2015

by

It is a new year and I can exploit that to write a post proclaiming how
something ought to be done in 2015. We can use the new year to discard last year’s practices and mistakes as “the old way” and start fresh from lessons that we’ve learned.

The interesting (and also most frustrating) part about building frontend apps is
how fast the landscape changes. The tools, libraries, and frameworks that you
use today might not be the same as what you’d end up using on a new project only
a month from now. While we’ve ended up with this culture of adopting something
new as soon as someone posts that the “old” way is “dead”, I’ve found a few
pieces of the frontend stack that I do not plan on switching out anytime soon.

I would also like to preface this with stating that this post is highly
opinionated. The opinions expressed here are mine and formed through my own
experiences. These opinions may not reflect what I end up doing in practice, nor
does it reflect on what others at Grio may choose or use.

read on