JavaScript Archives - Jeff Everhart

The Future of JavaScript and the Browser

I’ve been doing a deep dive into Vanilla JavaScript lately, partly as a pretty overt reaction to the proliferation of client-side MV* frameworks. My thought process is that the time spent learning frameworks isn’t necessarily transferrable beyond some of the high-level concepts they help you solve, things like routing, data-binding, and dependency injection. But, once […]

Read More

How to build an HTTP file server with Node.js

Over the last year or so, I’ve been working more and more with Node.js for a variety of projects. I started by building a few command line apps, progressed to some simple Node/Express sites, and more recently tackled some pretty complex apps that integrate RESTful web services that are hosted on AWS and Heroku. While […]

Read More

Building A Simple Heat Map with D3

Heat maps are a great way to analyze frequency in a data set. Beautiful and creative things happen when you are stuck in an airport for four hours. I’ve been wanting to explore heat map visualizations for awhile now, so when I had some time to kill flying back from SXSW, I decided to take […]

Read More

Creating a Video Streaming Classroom with AWS, Angular, and Google Material Design | Part 1

I’ve been thinking a lot lately about video streaming platforms used in the ed tech space, what makes them different from one another, and how feasible it would be to create one from scratch. After a short discussion with some people on the DEC team, I looked into the possibility of hosting and streaming video […]

Read More

The Pros and Cons of Using Google Sheets as an Application Backend

I’ve been doing more lately working with APIs of different sorts, and I recently stumbled onto some cool ways to use Google Sheets to connect with APIs and store the data very easily in a spreadsheet. Having completed the linked project in less than an hour, I was really interested in figuring out the pros […]

Read More

Debugging Node.js Processes | Error events.js 141

Debugging Node.js processes on the server can be kind of painful depending on what tools you have available to help you make sense of error messages. After scouring the web, it seems that a lot of people get frustrated by an error that gets thrown at events.js 141, which seems to be a generic socket […]

Read More