Slide 1

Slide 1 text

The State of JavaScript

Slide 2

Slide 2 text

@Jack_Franklin

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

https://gocardless.com/blog/how-we-built-the-new-gocardless.com/

Slide 5

Slide 5 text

things people keep tweeting 4

Slide 6

Slide 6 text

it’s difficult to get into front end web development 1

Slide 7

Slide 7 text

it’s difficult to get into front end web development it’s difficult to build client side applications

Slide 8

Slide 8 text

HTML + CSS + the odd bit of jQuery

Slide 9

Slide 9 text

complexity for complexity’s sake

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

it’s difficult to build client side applications 2

Slide 12

Slide 12 text

building client side applications is complex

Slide 13

Slide 13 text

http://www.smashingmagazine.com/2013/06/11/front-end-ops/ “application logic is being deferred to the client side. For some reason, though, operations folks aren’t going with it”

Slide 14

Slide 14 text

moving work to the client necessarily leads to a more involved, complex front end workflow (and that’s not a bad thing)

Slide 15

Slide 15 text

I constantly feel that I'm behind on my homework having to evaluate new libraries and frameworks showing up https://news.ycombinator.com/item?id=9604203 3

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

"But how can we get anything done when we’re spending most of our time learning?" http://www.breck-mckye.com/blog/2014/12/the-state-of-javascript- in-2015/

Slide 18

Slide 18 text

Stop trying to learn. Build things in whatever you’re comfortable with.

Slide 19

Slide 19 text

“As you get better, these new frameworks and tools become way less daunting and the anxiety caused by things moving too fast will subside.” http://wesbos.com/overwhelmed-with-web-development/

Slide 20

Slide 20 text

Focus on a higher level and remove the anxiety

Slide 21

Slide 21 text

deep knowledge of 1-2 tools you rely on is always superior

Slide 22

Slide 22 text

there are too many frameworks 4

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

in the last 12 - 24 months… backbone angular ember react

Slide 25

Slide 25 text

this is not a bad thing!

Slide 26

Slide 26 text

competition = improvement (ReactJS rendering)

Slide 27

Slide 27 text

“Why we moved from A to B and why A is rubbish”

Slide 28

Slide 28 text

pressure to be on the latest and greatest

Slide 29

Slide 29 text

use cases

Slide 30

Slide 30 text

don’t under value familiarity

Slide 31

Slide 31 text

GoCardless picked Angular

Slide 32

Slide 32 text

and now we’re quite good at it

Slide 33

Slide 33 text

“will you move from Angular to X?

Slide 34

Slide 34 text

https://roost.bocoup.com/2015/austin/blog/why-backbone/

Slide 35

Slide 35 text

so many considerations

Slide 36

Slide 36 text

https://twitter.com/padolsey/status/603203449803636737

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

no framework is good at everything no framework is bad at everything

Slide 39

Slide 39 text

libraries vs frameworks

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

npm unified package publication

Slide 42

Slide 42 text

proper dependency management and versioning!

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

ECMAScript 6 ECMAScript 2015

Slide 45

Slide 45 text

Release Candidate 4 https://people.mozilla.org/~jorendorff/es6-draft.html

Slide 46

Slide 46 text

goals of ES6 3

Slide 47

Slide 47 text

complex applications

Slide 48

Slide 48 text

libraries

Slide 49

Slide 49 text

code generation (compile to JS)

Slide 50

Slide 50 text

https://youtu.be/mPq5S27qWW8

Slide 51

Slide 51 text

block scoping arrow functions destructuring default parameters

Slide 52

Slide 52 text

adoption and familiarity

Slide 53

Slide 53 text

we’re not writing “straight up” JavaScript any more

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

testing grounds

Slide 56

Slide 56 text

=>

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

SystemJS

Slide 60

Slide 60 text

jspm http://javascriptplayground.com/blog/2014/11/js-modules-jspm- systemjs/

Slide 61

Slide 61 text

https://youtu.be/NpMnRifyGyw

Slide 62

Slide 62 text

http://www.bbc.co.uk/news/magazine-16444966

Slide 63

Slide 63 text

“Photographs will be telegraphed from any distance… striking events will be published… an hour later… photographs will reproduce all of nature’s colours.”

Slide 64

Slide 64 text

“Wireless telephone and telegraph circuits will span the world. A husband in the middle of the Atlantic will be able to converse with his wife sitting in her boudoir in Chicago.”

Slide 65

Slide 65 text

“There will be no C, X or Q in our everyday alphabet. They will be abandoned because unnecessary.”

Slide 66

Slide 66 text

things that will may (won’t) happen in JavaScript in the next 12-24 months… 8

Slide 67

Slide 67 text

…for complex web applications

Slide 68

Slide 68 text

fewer people will write JS without going through a compilation step 1

Slide 69

Slide 69 text

(TypeScript and Babel in particular)

Slide 70

Slide 70 text

Smaller libraries (and the composing of) will become more popular 2

Slide 71

Slide 71 text

Focus on libraries doing one thing well (MomentJS, Immutable) 3

Slide 72

Slide 72 text

The monoliths (Angular, Ember) will always have their place and use cases 4

Slide 73

Slide 73 text

The use of compilers like Babel will be abstracted away by build tools like jspm and Webpack 5

Slide 74

Slide 74 text

Running the same JS client side and server side will become more popular 6

Slide 75

Slide 75 text

and the phrase “Isomorphic JS” will die in a pit of fire 6.1

Slide 76

Slide 76 text

As ES6 implementations grow and stabilise, we’ll already be writing ES7 anyway 7

Slide 77

Slide 77 text

The rate of new frameworks will slow down 8

Slide 78

Slide 78 text

In 12 months, tweet me telling me how right wrong I was

Slide 79

Slide 79 text

@Jack_Franklin