Modern web development vs Debitoor

The talk was an overview of contemporary web-development buzz-words in comparison to what we have in Debitoor, as well as detection of what we miss to feel even better :)

	Concept / tech	Debitoor	Comment
.	Nice history	yes	crappy browsers -> server-side frameworks (php, asp, etc) -> lot of ugly js -> nice js and client-side rendering only, nice rest api for backend
.	Html5, Css3, app cache etc	yes	every single day
.	Web workers, svg, drag&drop, web gl (3d), websockets	no needs	not yet, but just give us a reason! :)
.	Modernizer, JQ, underscore	yes	debitoor boilerplate vs html5 boilerplate :) that's ok wanna try lo-dash.js instead of underscore..
.	JS Engines	yes	everything is backbone.js and it rocks!
.	Css preprocessing - Less	no	it could help us in having UI guidlines as constants used everywhere and easy to modify at one place; it will beautify our css at all
.	CoffeeScript	no needs	we will try if we are boring
.	Modularity	yes	sba namepspace function, backbone - it's ok.. but could be much more better
.	Dependency management, scripts loading	no	absent at all. we have only messed up scripts order in scripts.js.
.	Client side rendering, tempating	yes	jq templates could be replaced by a better templating engine though..
.	One-page App	no	will avoid extra ajax for top-menu and diff settings, will improve resource sharing and UX (eta - 2 days to switch)
.	Responsive design	yes	we don't change layout blocks for diff devices, but we use css and modernizer for small various hooks and tablets look good
.	Unit testing, code quality	yes	qunit -> jasmine -> mocha ? :) JSLint
.	Command line, automation	yes	npm prepares our front-end by 1 command (master, minification)
.	Dev tools	yes	chrome, sublime etc - everyone is passionate about his env

Conclusion - front-end stack at Debitoor is quite good and will be even better :)
Given by Alex (abu)