Talks which demonstrate innovation at either a technical or “best practice” level will be given preference. Your creation does not necessarily have to be in production, but we will insist on it being something more significant than a cool ten-line function you came up with (unless that function allowed you to control sharks fitted with lasers or something).
JSFoo 2013 is a single-track event. We invite proposals for:
- full-length 40-minute proposal
- a crisp 15-minute presentation
- sponsored sessions, 40 minute duration
- flash talks of 5 minutes duration. Submissions for flash talks will be opened one week before the event
- Hands-on sessions ranging from two to six hours on JS libraries, frameworks and tools. These proposals will be categorized as workshops
HasGeek believes in open source as the binding force of our community. If you are describing a piece of technology, we’d like it to be available under a permissive open source license.
If your software is commercially licensed or available under a combination of commercial and restrictive open source licenses (such as the various forms of the GPL), please consider picking up a sponsorship. We recognize 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.
You can submit a proposal to speak at JSFoo 2013 via the submission funnel below. Please describe your proposal in as much detail as possible. Detail is important if you’d like to be voted up into the schedule. In particular, we want to hear why you are the best person to be delivering a talk on your proposed topic. Provide links to previous talks and presentations you’ve done. This will help attendees and the programme committee in evaluating your proposal.
Making a funnel submission does not guarantee final selection.
Voting is open to attendees who have purchased event tickets. If there is a proposal you find notable, please vote for it and leave a comment to initiate discussions. Your vote will be reflected immediately, but will be counted towards selections only if you purchase a ticket. Proposals will also be evaluated by a program committee consisting of:
- Sunil Pai, Myntra
- Rakesh Pai, Errorception
- Barbara Maim, BangaloreJS and Minsh
- Jonathan Maim, BangaloreJS and Minsh
- Rajasekharan Vengalil (Raj), Microsoft
- Vishal Parpia, ActivElement
Proposers must submit presentation drafts as part of the selection process to ensure that the talk is in line with the original proposal, and to help the program committee build a strong line-up for the event.
There is only one speaker per session. Attendance is free for selected speakers. HasGeek will cover your travel to and accommodation in Bangalore from anywhere in the world. As our budget is limited, we will prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. If you are able to raise support for your trip, we will count that as speaker travel sponsorship.
If your proposal is not accepted, you can buy a ticket at the same rate as was available on the day you proposed. We’ll send you a code.
The program committee will announce the first round of selected proposals by 15th August and a second round by 2nd September. We will finalize the schedule by 7th September. The funnel will close on 25th August. The event is on 20th and 21st September 2013.
As the browsers continue to evolve and become more powerful, the application architectures tend to move more towards the client than the server, enabling the browser to do most of the heavy lifting, while providing a seamless experience to the users. However, as the applications grow, so does their memory footprint.
We’ll be taking a look at some of the real applications and analyzing them for memory leaks. Also, we’ll find out the real reasons behind the leaks, fix them and profile the application to compare the results.
Jaideep has been speaking at different forums about the front-end practices and workflows and believes that jumping to any frameworks without an understanding of the core generally leads to code which is less optimum and harder to debug.