(Skip ahead to session proposals)
About JSFoo
JSFoo is India’s only national JavaScript conference. The first season of JSFoo featured editions in Bangalore, Pune and Chennai between Oct 2011 and Feb 2012. The second edition in Bangalore in Oct 2012 was based on the theme “JavaScript Everywhere” – featuring JavaScript on web servers, embedded in robots, as a cross-platform language for mobile, and in its original home, the browser.
##JSFoo 2013
The theme for JSFoo 2013 is original creations with JavaScript. Showcase innovative work done with JavaScript – if you have created something at work or outside your work commitments, with or without a business model in sight, something you’ve done for the love of seeing it come to life in front of your eyes, JSFoo is the place to talk about it!
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).
We are also accepting high quality talk and workshop proposals on JS frameworks, libraries and tools. These proposals have to provide clear objectives and take-aways for practising JavaScript developers.
##Format
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
Commitment to open source
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.
Speaking submissions
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.
##Selection Process
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.
Tickets: http://jsfoo.doattend.com
Website: https://jsfoo.in/2013
Dates
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.
KM
Karan Misra
@kid0m4n
node.jsfoo: Internals Explained
Submitted Aug 1, 2013
Section:
Crisp Talk
Technical level:
Intermediate
To introduce the audience to the various nuances of doing async programming right. To break that mental barrier in understanding the internal “tick-tock” of the node.js engine
Outline
A lot of us probably have done callback based aync coding. Some of us might even have dabbled in promises (Q), etc.
However, do we really understand what makes async tick? When is the callback going to be executed? What is process.nextTick()? Why does JavaScript lack the sleep(x) method. How are threads involved in this whole party. Can we avoid callbacks altogether? What idiomatic patterns can help keep sanity in a large node.js codebase.
Having a deep understanding of the same will allow us to tackle node.js performance issues as they crop up (and they will!) I will end the talk by demonstrating a real life scenario on the optimizations we had to do to remove the ORM bottleneck from a node.js application which absolutely had to scale
Requirements
Inquisitiveness to learn the internals of node.js; of what makes the clock tick
Speaker bio
Having spent the last 8 months in a real world node.js project, this fervent Rubyist has developed a deep appreciation of concurrency and all things async.
Getting the first enterprise grade node.js application at ThoughtWorks to production took some doing; adopting idioms which seemed foreign at first, but have become second nature now.
A pragmatist at heart, I always strive to understand the internal workings of a system so as to be able to take the best design decision possible given the circumstances. This journey required me to dig deep into node.js as we not only had to keep the code maintainable, we had to keep it performant at any cost.
Having said all that, I believe I will do justice to the topic proposed; its going to be helluva 15 minutes.
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}