Collection of talk abstracts

javascript-23rd-century.md

JavaScript Architecture for the 23rd Century

Centuries ago when JavaScript was a browser toy to flash things around on the page, the need for architecture in JavaScript was non existent. You could simply throw some jQuery into a file, or even just in an embeded script tag on the page and you'd have what you need.

Centuries later in the 23rd century, Stardate 1312.4, the need for architecture is critical in creating long term JavaScript Applications that will survive a 5 year mission into deep space.

First we will step back in time to talk about the constructor pattern, and move forward through time into other useful patterns such as modules, and namespacing. Then move into talking about organizational strategies as well as AMD and Browserify.

Finally we'll talk more about JavaScript in the 24th century with ES6 classes and how we can utilize them today with Traceur. Cadets who attend this session will learn:

• Review Constructors
• Module patterns
• Namespace pattern
• File organization
• AMD
• Browserify
• ES6
• Tracuer

I like the idea a lot, something more general than "here's how you do architecture in Angular". I'm concerned a bit about it being too much info, especially with the Traceur content, so be sure to practice it for whatever time-box you're targeting.

Some notes:

• missing "t" in the title
• That star date is in the 24th century. ;)
• Instead of "long term" maybe use something a bit stronger like: "sustainable and easily maintained"?
• Instead of saying "the goal of this talk" be assertive with something like "First we will step back in time..."
• If you look at some of the really popular and well received talk abstracts you'll find that most have some bit about what attendees will get from the session. It's a bit of recap, but can also serve to show the value proposition of accepting this talk over another on the same topic.

Good luck!!

I'm just going to be completely honest after being a part of the program committee for Fluent for two years: this abstract tries too hard. I want you to have a successful abstract, so let's get down to it...

First off, I commend you for taking a more creative approach to talking about JavaScript. However, there are a few problems with the way you currently have this setup...

• Gary Bernardt already did something similar to this and that was the first thing I thought of
• As Jordan Mentioned, it's WAY to broad in scope for a Fluent session. It tries to pack too much in. You could do an entire session on any one of the above topics.

The key to getting selected for Fluent is to have an abstract that addresses one issue and does it well. You will want to submit multiple abstracts with this same strategy. Here are some ideas...

Tracuer Inside And Out
A comprehensive dive into the Tracuer precompiler

IE 11 vs Chrome. DevTools Smackdown
A side-by-side comparison of DevTools in IE vs Chrome. I put this one down since you are an IE MVP.

Introducing WebPack
Browserify is old. AMD is old. WebPack is NEW and awesome and does a LOT.

I hope I wasn't too harsh, but I want to help in making sure you get selected. However, now that I think about it, the CFP may already be closed so my advice may come too late.

In any event, good luck and remember that I am frequently wrong. :)