In 2011, Node.js put JavaScript firmly in the backend, making JavaScript developers productive at both ends of the stack, and making it possible for business logic to finally be moved into JavaScript.
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 2013, we went wild thinking of all the possibilities. JavaScript phones! Robots!
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?
In 2014, JavaScript is no longer a toothless child or a rebellious teenager that wants to do everything itself. JSFoo 2014 is about working with JavaScript as the centerpiece of a complex web stack.
Format
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
Criteria to submit
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.
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.
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.
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 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.
HK
Himanshu Kapoor
@fleonus
Automating Mundane Front-end Tasks Using Node.js
Submitted Aug 7, 2014
Section:
Workshops
Technical level:
Intermediate
Laziness is one of the three virtues of a good programmer, says Larry Wall, the original author of the Perl programming language: http://threevirtues.com/
Such a good programmer would understand how mundane it is to perform a task repeatedly. He considers it grunt work, and he’d rather write a bot to do the task for him, so that he never has to do it again.
The world of front-end development has been making quite some advancement in automation. Scaffold tools like yeoman, build systems like grunt, and package managers like bower have made the lives of developers a lot easier. But even still, the friction of using such tools is rather high.
This workshop will not only demonstrate how tooling can help you automate your day-to-day tasks, but also provide a deep understanding of the underlying functionality behind such tools. There might be some friction to begin using such tools, but once you get the hang of it, they can make your development process a lot easier and faster.
Outline
The workshop would begin by introducing tooling for Front-end development. Examples would include scaffold generation using yeoman, build processes using grunt, and dependency management using npm and bower.
After this introduction, the underlying configuration and functionality behind such tools will be detailed. The most part of this workshop will describe automation of real-world grunt tasks, like concatenation, minification, source map generation, running tests and internationalization.
Some of these tasks might need some tailoring, depending on the kind of project one is working on. If configuring an existing task cannot do such tailoring, the workshop would go about writing a custom task to automate such a process. All it takes is writing some logic in Node.js after all.
Requirements
The attendees are expected to have intermediate knowledge of JavaScript and Node.js. For best results, it is recommended to have the latest versions of Node.js and NPM installed before attending the workshop.
Speaker bio
Himanshu is a front-end engineer at Wingify. He has been working with JavaScript for the past 5 years, and has done several projects based on front-end frameworks like Backbone, Ember.js and most recently Angular.js. His role at Wingify involves solving challenges related to data visualization, communication and performance optimization on the front-end.
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}