search

lnug / speakers

Open an issue to submit a talk
https://github.com/lnug/speakers
43 stars 7 forks source link

The state of web asset pipelines and the description of a new pipeline that combines the best of all worlds. #29

Closed insidewhy closed 9 years ago

insidewhy commented 9 years ago

People soon realised that a task runner is not an asset pipeline, maybe sometime after the millionth spaghetti gruntfile was written. Along came gulp, the wonderful streaming pipeline, but the people saw that it was flawed, being built around 1:1 operations (disallowing nice n:1 stuff such as concatenation of streams together with their source maps).

Then came plumber, broccoli, gobble, and metalsmith, all with unique selling points yet all having drawbacks not found in grunt and/or gulp.

It was time for a new asset pipeline to be born out of the pain of trying to find the holy grail of asset pipelines. It was time to write it using functional reactive programming, ES6 and a geekgasm of buzz-words to seduce the JavaScript community. It was time for a bullshit sensationalised lnug talk abstract. Yes, it's time to sigh. sighjs.

In this talk I will describe the issues with existing asset pipelines (read: trash all the competition) and describe how sighjs improves upon the state of the art (read: gloriously inflate my ego).

This talk will last around 10 minutes long and it will be a little surreal. Here is one of my other talks at HNN.

orliesaurus commented 9 years ago

YES!!

iancrowther commented 9 years ago

If you can make it 20 mins then I'm keen to see how this one unfolds.

olizilla commented 9 years ago

+1 for surrealism in tech

insidewhy commented 9 years ago

@iancrowther Yeah it's about 20 minutes worth of material but I'm planning on rushing through it.

orliesaurus commented 9 years ago

Try not to rush it then please

insidewhy commented 9 years ago

@iancrowther Could you schedule it for May, thanks! @orliesaurus George Ornbo's talk started late and he had to rush but it made the talk even better I think - rushdown style.

orliesaurus commented 9 years ago

haha yeah but that wasn't because he wanted to, that's because we had no more time left :P Anyway we don't mind shorter talks, in fact we're gonna have lightning talks soon!

insidewhy commented 9 years ago

@orliesaurus haha yeah I know he had to rush, I thought it might be cool to intentionally go fast though. Yet there's a lot of material to cover so a lightning talk might not be long enough.

I've already planned most of the talk, but I want to spend some time adding some even cooler stuff to sigh and working on the animations in the slides.

iancrowther commented 9 years ago

@nuisanceofcats get in touch with @simonmcmanus to see if your talks can complement each other at all.

https://github.com/lnug/speakers/issues/27

Do you prepare images? @simonmcmanus do you consume images etc..

insidewhy commented 9 years ago

@iancrowther sigh asset pipelines can transform any type of file, including images. I'm planning on adding more specific API around dealing with binary data and caching files out to the fs (or a virtual/shared memory fs) when necessary.

simonmcmanus commented 9 years ago

@iancrowther @nuisanceofcats My talk will cover things like Duo (duojs.org) and browserify transforms. Both of which could be a part of an asset pipeline but I wont be covering those aspects in my talk.

I could mention that asset pipelines will be discussed in more detail in the following talk and link them in that way.

insidewhy commented 9 years ago

Sorry for the noise, I deleted my previous comments in favour of pushing the github repository earlier than I had planned:

sigh external

As you can see sigh overlaps with duo quite a lot!

iancrowther commented 9 years ago

It would be great if you're talks compliment each other, have a chat maybe if both of you list some topic points etc in your proposals..

its not mandatory but would help add some polish to the event

simonmcmanus commented 9 years ago

@nuisanceofcats - that is interesting, Duo definitely has some pain points and it looks like you might be working in those areas.

insidewhy commented 9 years ago

@simonmcmanus Yep I tried it a bunch and there were some aspects that I thought were pretty flawed and could be done much better. I think sigh+sigh-external's approach will be better because:

  1. More external repositories supported, npm/bower/github
  2. Will maintain your package.json/bower.json so that requires without versions like require("bower:package") will be fixed for everyone who uses your repository in the future.
  3. Won't have to type the same versions over and over again.
  4. Source Maps.
  5. Watches your files for changes with incremental rebuilds.
iancrowther commented 9 years ago

Apologies for the scheduling confusion

insidewhy commented 9 years ago

Added some great new features recently! :)

orliesaurus commented 9 years ago

Are you happy to present this month @ohjames ?

insidewhy commented 9 years ago

Yep :+1: