Comments on: On the Challenge of Developing JavaScript Within a Team

By: Radoslav Stankov

Radoslav Stankov — Tue, 14 Jul 2009 18:54:43 +0000

I haven’t work with more than 2 js developers. But I think that conventions and frameworks should be decided in the beginning. That using tools like sprockets for managing dependencies and sub-libs like my CD3Widgets Behaviors ( https://github.com/RStankov/controldepo-3-widgets ) will help a lot.
I think for the js work we should learn form the frameworks in the manner of managing work / code / responsibilities. And still serious js development is still in yearly stages.

By: Kris

Kris — Mon, 08 Jun 2009 23:21:23 +0000

I’m curious to read your findings, and your current approach. I always get a little self-conscious when I think about my coding style — I tend to change my mind (and my style) a lot, which is not a good thing. I’ve written a lot of Actionscript lately which has definitely altered the way I write JavaScript, which in turn has changed the way I write PHP. For better or worse.

By: Dan Dean

Dan Dean — Tue, 02 Jun 2009 00:58:20 +0000

I've been thinking about this too. This is one of the unfortunate consequences of JavaScript typically being the secondary discipline of the author. People tend to be either server-side devs then JS devs, or html/css devs then JS devs. Our approach to JavaScript is then highly influenced by where our primary interests lie. This makes for an interesting (if sometimes galling) experience for those of us whose primary interest is in JavaScript.

By: Jonathan Arkell

Jonathan Arkell — Mon, 01 Jun 2009 23:00:05 +0000

This is further amplified by the fact that Javascript can be used procedurally, functionally or object oriented. Even in its OO, it is natively prototype based, but there earen’t that many (it seems) who know how to work with prototype OO.

JS provides the rope…