JSFoo 2016

Tackling speed and performance for JavaScript

About JSFoo

JSFoo is India’s premier JavaScript conference. We launched JSFoo in 2011 as India’s first JavaScript conference. The JS community in India has grown phenomenally since. JavaScript now pervades every aspect of web development – browsers, apps, front-end, backend, mobile, and IoT.

JSFoo 2016: Theme

Over the last few years, JavaScript has evolved to become the centerpiece of a complex web stack. Today, it is a prime subject of the obsession that lies with performance and speed. How can you get pages to load faster? How do you work with browser constraints to enhance speed? How do you measure performance? What actually is performance? In what ways do faster response times influence your architecture choices and plans? How is this new focus on faster page loads and apps working offline influencing the development of front-ends and backends as well as server side JS?

The theme for the 2016 edition is tackling speed and performance for JavaScript.

We are inviting full talks (40 mins), crisp talks (15 mins + 5 mins Q&A), and 3-6 hour long (hands-on) workshops from practitioners on the overall theme of speed and performance, including the following topics:

  • Architecting for performance – case studies on how you got faster response times
  • Best practices: debugging and profiling on the web, measuring performance
  • Handling large volumes of data in the browser
  • Building and deploying web apps eg webpack, travis
  • Modern web technology: Angular 2, React
  • Universal JavaScript: meteor js
  • Progressive Web Apps
  • JS off the web – raspberry pi, IoT
  • The cutting edge: elm

This year, JSFoo will feature two days of talks on JavaScript (15-16 September) and a single day of talks on design (17 September) at Meta Refresh (call for proposals will open shortly).

Guidelines for submission

Every proposal MUST be accompanied by:

  • A three minute preview video where the proposer gives an elevator pitch about the talk.
  • Detailed outline of the talk – either in the form of draft slides, mind map and/or textual description.
  • If you are proposing to speak on a topic where the code is not open-sourced yet, the editorial panel will consider your proposal only if the code is made open-source at least three weeks before the conference.

Without the above information, your proposal will not be considered for review.

If you are submitting a Workshop Proposal, you must clearly state:

  • Background knowledge that participants must possess in order to attend your workshop.
  • Details and links to software / packages which participants must install before coming to the workshop.
  • Laptop configuration.
  • Links to background reading material and GitHub repos.
  • Duration of the workshop.
  • Maximum number of participants who can attend your workshop.
  • Instructor’s past experience with conducting workshops.

There is only one speaker per session. Workshops can have two or more instructors.

Entry is free for selected speakers.

Due to budgetary constraints, we prefer speakers closer to home. But if we think you stand out, we’ll provide a grant to cover part of your travel and accommodation to Bangalore. Grants are limited and are made available to speakers delivering full sessions (40 minutes or longer) only.

Commitment to open source

HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like for it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a sponsored session.

Important dates:

Deadline for submitting proposals: 29 August 2015
Conference dates: 15-16 September

Venue

JSFoo will be held at the MLR Convention Centre, J P Nagar.

Contact

For more information about speaking proposals, tickets and sponsorships, contact info@hasgeek.com or call +91-7676332020.

Hosted by

JSFoo is a forum for discussing UI engineering; fullstack development; web applications engineering, performance, security and design; accessibility; and latest developments in #JavaScript. Follow JSFoo on Twitter more

ranadeep bhuyan

@ranadeepbhuyan

Progressive web application for Speed using Google Polymers

Submitted Aug 12, 2016

Context – Starting with the learning from past mistakes – with couple of question to audience

Looking back to the history of web application development using HTML2 and HTTP/1.1, the web has evolved through a numerous tides of reactive measures in order to address some of major real world problems. We have come across number of client side technologies starting from introducing javascript into the browser till the time of desperate insertion pollyfils (to support a few HTML specs) into the browser platform. As well in the server side – we have made a lot of improvements from the world of ASP/JSP to SOAP/REST and Push servers.

On the user experience side – the industry has evolved with single page architecture with various javascript frame works and tools.

At times, when we start with new web application or re-architecture of an old application we all have to take a difficult decision at the beginning – that is, ‘what framework and tech stack are we going to use?’ Once the decision is taken we are stuck with the decision at least for two years or till we decide on the same decision again.

The ideal state to be in is possibly are the following attributes –
Super fast first page load from any full url within the application, quickly become responsive to the user actions, rich user experience (app-like) and reliable offline, works mostly with no/poor network. Reusability is one of the major factor as well.

Many of the current frameworks have been trying to solve for this ideal state in parts or in combination of a few for example SPA with serve side rendering. We are yet to see any magical combination of both server and client technologies coming together to solve for the wish list of the ideal state. There may be various reasons to this – like technical companies has competitions from each other, less collaborations, researchers are working in silo etc. As a result of this, almost all small or large organizations are creating large monolith stacks every now and then. Some of us are doing tech stack revamp every year and ends up creating another new monolith after two years.

What can we do to reach the ideal state?

How do we combine or develop specific tools and technologies to solve for developers and for customers as well –is this real paradigm shift for developers, browser companies and server technologies? Or is this a matter of coming together once for the community and customers to align to a single goal with single priority.

Let’s see how a Single page application built in (any) react JS frame work using HTTP2 push, service worker can achieve to the maximum for the above wish list of ideal state. We follow some of the best of the practices borrowed from the 17 UNIX philosophies (for Unix commands/programs).

We will demo a few small re-usable components using ReactJS and Google Polymers.

To Conclude - Modern browser should support couple of basic things like import, Custom elements for a better progressive web development for Speed. HTTP 2 and Polymers are currently the best combinations to work with web scalable and re-usable applications with all possible goodies like first page load, offline, re-usable etc.

Outline

  1. Pain points
    - Solutions evolved so far
    - Ideal State
  2. Progressive web
  3. Google polymers
  4. Demos
    • Server Push
    • Couple of Map polymers
    • Re-Usable Polymers for IOT

Requirements

Setting the context - 2 mins
Couple of learning from a few historical coding issues with HTML (with demo) - 4 mins
Ideal state - wish list - 5 mins
(Fast first load ready to use, App like rich UI, usable at offline mode, accessibility)

Pain points on existing solution (code demo) - 4 mins
(Couple of Current JS frameworks, services – a comprehensive Comparison slide, Custom UI elements, 2 way data binding, first page load time etc.)

Why Google Polymers? – Trying to address ideal state along with HTTP 2 Push
(UNIX like to our basic HTML/JS/Server programming practices) - 5mins

Progressive web application demo – 4 mins
(Using Server side rendering, Server Push, pre-cache, service worker, pre-render)
Accessibility - 2 mins
Re-usability - 3mins

Demo Few Re-Usable Polymers we have created
Google Maps elements – (demo 3 mins)
LED hello world demo - 2 mins
AR Parrot drone re-usable control Polymer with Node JS –(demo 3 mins)

Limitation of Polymers and temporary fix - 2 mins

Github code share – 1 min
Q&A – 4 mins

Speaker bio

We are from Intuit and passionate about Google’s idea of Speed and trying change the way we develop web applications at Inuit to deliver for customers and developers in a boundary less manner.

Ranadeep has been developing rich web applications including mobile apps for more than a decade using various cutting edge technologies on native and JavaScript technologies. Ramit brings a rich web application development experience from past experience in Commonfloor.com and now from Intuit. Both of them work for their flagship product devision of Small Business Groups - QuickBooks offering and www.intuitmarket.com a high scale websites.

Links

Slides

http://bit.ly/2bwRbN6

Comments

{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Hosted by

JSFoo is a forum for discussing UI engineering; fullstack development; web applications engineering, performance, security and design; accessibility; and latest developments in #JavaScript. Follow JSFoo on Twitter more