JavaScript in 2015

Post by mattdesl » Wed, Jan 07, 2015, 3:21 PM UTC

davedx wrote: post #48

arcatek wrote: post #46

Earlier quoted context omitted.

In their current states, Webpack is for the production applications, JSPM for development / little ES6 apps, and SystemJS is used for Node.js. - Webpack supports much more than just ES6 (and more people work on it), so you probably want to use it for production apps. - JSPM allows you to load ES6 library by transpiling them on-the-fly, which is great for simplicity. - SystemJS works by itself in a Node environment, y…

This seems so fragmented, even before you consider all the other module loaders, transpilers and toolchains. I'm a senior frontend developer and I find this side of JavaScript truly bewildering.

Post by williamcotton » Wed, Jan 07, 2015, 3:25 PM UTC

lhorie wrote: post #49

khalilravanna wrote: post #37

Earlier quoted context omitted.

That's assuming you want all your scripts to be loaded on the front end asynchronously which seems to be only for development. For production I think you'd still want to compile this all down for a faster load time. From the jspm page: "For production, use the jspm CLI tool to download packages locally, lock down versions and build into a bundle." So I think you're correct that there'd be no build step for developmen…

yep, the point though is that having a build step during dev adds some overhead (which can easily go into the several seconds range in my experience) into the type-save-reload cycle, which is exacerbated by hit-reload-before-build-finished-so-need-to-reload-again pattern. My understanding is that this tool removes that entire class of annoyances, and gives a no-hassle live-reload ES6-enabled environment on top.

  var collections = require('npm:lodash-node/modern/collections');
  var $ = require('github:components/jquery');

Post by sbuccini » Wed, Jan 07, 2015, 3:31 PM UTC

tmaly wrote: post #17

I would love to hear more about djgif

Post by insin » Wed, Jan 07, 2015, 3:38 PM UTC

moron4hire wrote: post #60

hfsktr wrote: post #43

Earlier quoted context omitted.

I know what the batman example gives but I don't get how it's a WTF? I assume the expected output is "wa" but why should a string less an integer produce that?

No, it produces NaN (Not-a-Number), and then repeats it in a string 16 times. The WTF is that NaN can be concatenated to strings as "NaN".

Post by lbotos » Wed, Jan 07, 2015, 3:39 PM UTC

radiowave wrote: post #55

lbotos wrote: post #41

Aside: "A DJ using Ableton Live, a huge bundle of MaxMSP emitting a UDP stream of beat information (courtesy of the immensely pro Cade), a UDP ➝ WebSockets server, and DJGif pulling hundreds of GIFs off various Tumblrs to beatmatch on two projectors makes for a hell of a good show." Does anyone know why he wouldn't have used the midi clock from Ableton (or other DJ software) to a "midi->websocket" server?

One reason might be that MIDI clock is just a repeating, identical message. It does not contain any position information (like where the next bar starts). To get positional information relating to beats and bars, you need to use MIDI Song Position Pointers, however these use a 14 bit counter which will typically overflow after about 10 minutes. In short, long-running musical clock sync over MIDI is problematic. For s…