Why JavaScript web applications should embrace traditional URLs - 9elements
Why JavaScript web applications should embrace traditional URLs In this article, I will first take a high-level look at modern frontend architectures: In a time where web apps easily surpass 1 MB of JavaScript, what should we try to achieve? Second, based on these considerations, I’m going to argue that Backbone.js should fully support the traditional HTTP URL scheme. The ideal web site architectu
Patterns for Managing Large Scale Backbone Applications | Ben Howdle
I write JavaScript for KashFlow. Catch my designs on Dribbble, my code on GitHub, talk to me on Twitter, or talk more on Skype or Email. Patterns for Managing Large Scale Backbone Applications24 March 2013 Backbone is frickin’ awesome. What I feel makes it awesome is the fact that it helps you write and structure better JavaScript code and not better “framework-x” code. It’s amazingly intelligent
[O'REILLY]Developing Backbone.js Applications -
Available free for open-source reading below or for purchase via the O'Reilly store. Pull requests and comments always welcome. Prelude Not so long ago, “data-rich web application” was an oxymoron. Today, these applications are everywhere and you need to know how to build them. Traditionally, web applications left the heavy-lifting of data to servers that pushed HTML to the browser in complete pag
DailyJS: Backbone.js: Hacker's Guide
There’s no denying the popularity and impact that Backbone.js (License: MIT, GitHub: documentcloud / backbone) by Jeremy Ashkenas and DocumentCloud has made. Although the documentation and examples are excellent, I thought it would be interesting to review the code on a more technical level. Hopefully this will give readers a deeper understanding of Backbone, and as the MVC series progresses these
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
