047 JSJ Specialized vs Monolithic with James Halliday and Tom Dale

Panel

Tom Dale (twitter github blog Tilde Inc.)
James Halliday (twitter github substack.net)
AJ O’Neal (twitter github blog)
Jamison Dance (twitter github blog)
Merrick Christensen (twitter github)
Joe Eames (twitter github blog)
Tim Caswell (twitter github howtonode.org)
Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up)

Discussion
01:52 - James Halliday Introduction

browserify

02:37 - Tom Dale Introduction

iCloud
Ember.js
Big Data & Hadoop

04:47 - Specialized vs Monolithic

github.com/tildeio
Idiology
Micro Libraries

14:13 - Learning Frameworks

18:04 - Making things modular

25:23 - Picking the right tool for the job

27:44 - voxel.js & emberjs

emberjs / packages
BPM - Browser Package Manager
NPM - Node Packaged Modules

testling-ci

Backbone.js

38:19 - Module Systems

CommonJS

41:14 - Cloud9 Use Case

43:54 - Bugs

jQuery Source Code

Picks

jQuery 2.0 (Merrick)
ECMAScript 6 Module Definition (Merrick)
AMD (Merrick)
Yiruma (Joe)
Elementary (Joe)
Miracle Berry Tablets (AJ)
The Ubuntu You Deserve (AJ)
Bravemule (Jamison)
RealtimeConf Europe (Tim)
visionmedia / cpm (Tim)
Why I Love Being A Programmer in Louisville (or, Why I Won’t Relocate to Work for Your Startup: Ernie Miller (Chuck)
Is Audio The Next Big Thing In Digital Marketing? [Infographic] (Chuck)
testling-ci (James)
voxel.js (James)
CAMPJS (James)
Discourse (Tom)
Williams-Sonoma 10-Piece Glass Bowl Set (Tom)
The Best Simple Recipes by America’s Test Kitchen (Tom)

Next Week
Why Javascript is Hard
Transcript
JAMISON: You can curse but we will just edit it out and replace it with fart noises.

TOM: I’ll be providing plenty of my own.

[Laughter]

JAMISON: Okay, good.

[Hosting and bandwidth provided by the Blue Box Group. Check them out at Bluebox.net.]

[This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.]

CHUCK: Hey everybody and welcome to Episode 47 of the JavaScript Jabber show. This week on our panel, we have AJ O’Neal.

AJ: Yo! Yo! Yo! Coming at you not even live!

CHUCK: [Laughs] Alright, Jamison Dance.

JAMISON: Hi guys, it’s tough to follow that.

CHUCK: Merrick Christensen.

MERRICK: Hey.

CHUCK: Joe Eames.

JOE: Howdy!

CHUCK: Tim Caswell.

TIM: Hello.

CHUCK: I’m Charles Max Wood from DevChat.tv. And this week, we have two guests. The first one is Tom Dale.

TOM: Hey, thanks for having me.

CHUCK: The other is James Halliday.

JAMES: Yep. Hello.

CHUCK: Welcome to the show, guys. We were having a conversation a while back, I don’t remember if it was during another episode or after another episode. But we were having a discussion over code complexity and having like small simple libraries or small simple sets of functionality versus large monolithic sets of functionality, and how to approach those and when they’re appropriate. So, we brought you guys on to help us explore this because you're experts, right?

TOM: I don’t think that’s a fair analysis of the situation, but we can certainly fumble our way through something.

[Laughter]

CHUCK: Alright. So, why don’t you guys, real quick, just kind of introduce yourselves? Give us a little background on what your experience is so that we know which questions to ask you guys.

James, why don’t you start? I know you’ve been on the show before.

JAMES: Hello. I suppose I wrote Browserify which is relevant here. It’s a common JS style, bundler packager thing that just uses NPM. And I have a bunch of other libraries. And I really like doing data development as just a bunch of little modules put together. They are all published completely independently on NPM. I think I’m up to like 230-ish some odd modules on NPM now. So, I’ve been doing that and I really like that style.

Special Guests: James Halliday and Tom Dale.

Search

Trending Now

Popular Searches

Show Notes