Theme this year: The broad theme this year is going to be Building Reliable Web Apps. Please refer to the Topics section below for the subject of talks and workshops we are looking for.
We are inviting proposals for:
Full-length 40 minute talks.
Crisp 15 minute talks.
Sponsored sessions, of 15 minutes and 40 minutes duration (limited slots available; subject to editorial scrutiny and approval).
Hands-on Workshop sessions, 3 and 6 hour duration.
Proposals will be filtered and shortlisted by an Editorial Panel. Please make sure to add links to videos / slide decks when submitting proposals. This will help us understand your speaking experience and delivery style. Blurbs or blog posts covering the relevance of a particular problem statement and how it is tackled will help the Editorial Panel better judge your proposals. We might contact you to ask if you’d like to repost your content on the official conference blog.
We expect you to submit an outline of your proposed talk – either in the form of a mind map or a text document or draft slides within two weeks of submitting your proposal.
You can check back on this page for the status of your proposal. We will notify you if we either move your proposal to the next round or if we reject it. Selected speakers must participate in one or two rounds of rehearsals before the conference. This is mandatory and helps you to prepare well for the conference.
A speaker is NOT confirmed a slot unless we explicitly mention so in an email or over any other medium of communication.
There is only one speaker per session. Entry is free for selected speakers. As our budget is limited, we prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. HasGeek provides these limited grants where applicable: two international travel and accommodation grants, three domestic travel and accommodation grants. Grants are limited and made available to speakers delivering full sessions (40 minutes or longer). Speaker travel grants will be given in order of preference to students, women, persons of non-binary genders, and individuals for Asia and Africa first.
Updated (19 April 2017): We are currently looking for talks in the following topics:
Testing: Testing tools and strategies; test driven development and testing culture; continuous integration and testing workflows; and case studies around testing your application.
Performance optimization: Performance analysis tools and techniques; best practices for building performant applications; browser, NodeJS, and framework internals; network protocols; and performance case studies.
Crash and performance monitoring: Monitoring applications for crashes and performance issues while in production.
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”.
Deadline for submitting proposals: 15 June 2017
Conference dates: 15–16 September 2017
For more information about speaking proposals, tickets and sponsorships, contact email@example.com or call +91 76763 32020.
Note: We aren’t accepting any new talks.
Virtual DOM, Real Problems
Virtual DOM has become the primary method of abstracting the DOM. However, the lack of clarity in understanding how the virtual DOM actually works leads to multiple inefficient techniques used when coding applications which are meant to be performant at scale.
In this talk, we plan to talk about how the virtual DOM works, how is it different from Shadow DOM used by frameworks like Polymer (Hint: almost completely), What are the differences in Virtual DOM implementations in different popular frameworks (Psst… Virtual DOM is NOT a standard), how to performance test an app that massively uses virtual DOM manipulations at scale, and tips to ensure how to ensure you get the maximum value out of your virtual DOM implementation, no matter what framework you use underneath.
- What is Virtual DOM (and why it is so cool!) - 3 mins
- Differences between Virtual DOM models used by different frameworks - 5 mins
- I use a Virtual DOM framework, but my app is so slow… Why? - 7 mins (includes 3 mins of performance testing interspersed)
- Quick Tips to ensure you always get the most out of your virtual DOM implementation (2 mins)
Basic understanding of the DOM. Experience with a framework which uses Virtual DOM is an added bonus, but not required.
Navin is a Full stack developer who goes about building cool stuff at Bloomreach Inc. He has worked with front end technologies for over a decade, from projects ranging from toy samples at hackathons to enterprise software with rigid requirements of performance. He has dabbled around with frameworks ranging from JQuery (which he loved back in the hey day), AngularJS (which he adored), React (which he dislikes), Vue (which is his new sweetheart) to Mithril (which he is hoping gains popularity). He is an open source contributer. In his free time, he enjoys talking about himself from a third person perspective.