In 2012, AngularJS made us think about moving business logic completely into the client-side as an actually sensible idea. Meteor give that idea two thumbs up.
In 2014, it’s time for some sobering up. The backends we built over a decade in Ruby and Python aren’t going away. New languages like Go and Hack are tantalising us with new possibilities. Our applications are increasingly distributed, often involving third party APIs. In such a scenario, where does your business logic reside?
This year’s edition spans four days, with two days of workshops and two days of conference. All days feature a single track. We invite proposals for:
- Full-length 40 minute talks
- A crisp 15-minute presentation
- Sponsored sessions, 40 minute duration
- Flash talks of 5 minutes duration. Submissions for flash talks will be accepted during the event
- Three hour workshops where everybody gets their laptop out and follows along
You must be a practising web developer or designer, and must be able to show how your own work has advanced the state of the web in the past year. You are expected to present original work that your peers — this event’s audience — recognise as being notable enough to deserve a stage.
If you are excited about someone’s work and believe it deserves wider recognition, we recommend you contact them and ask them to submit a proposal.
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.
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 editorial panel build a strong line-up for the event.
There is only one speaker per session. Entry is free for selected speakers. HasGeek will cover your travel to and accommodation in Bangalore from anywhere in the world for speakers delivering full sessions (30 minutes or longer). 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.
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 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.
Web Components - Fundamentals and Case Studies
Web Components, a set of new standards, is set to change the way we build the Web. You will walk away with a clear knowledge of why and how you need to use Web Components. The first part of the session will be on the fundamentals of Web Components and the latter will be on case studies which show some of the Web Component “Magic”.
We’ll start with the current state of the web and the proposed solution. We’ll then make a quick tour of the building blocks of the Web Components,
- Shadow Dom
- HTML Templates
- Custom Elements
- HTML Imports
each of which is a W3C standard.
We then move on to the case studies which show the power of Web Components and how quickly and elegantly we can reuse code.
Some of the scenarios include,
- Make a Polymer component talk to an X-Tag component.
- Show the same component working inside Ember, Angular and may be some other framework with minimal code change.
- Take a look at what other people are already building with Web Components.
In the end, we’ll talk about when is it not a good idea to make something a Web Component.
- Ablility to empathize with the pain of figuring out which div contains which div in a document and wondering how we ended up with a 20-level div hierarchy for a fairly simple application.
- Hope that things can change for the better.
A member of Adobe Dreamweaver Development team, Bhargava has been working at Adobe for more than 6 years. His interests include web development, data analysis, data visualization and building tools to help others with the same. He has contributed to open source IDEs like Brackets. He likes talking about himself in third person.