#Single-Page-Apps
7 notas · última:
Why Rails 5 / Turbolinks 3.0 / Action Cable matter, and why @dhh was right all along
The post argues that Rails 5 keeps the speed and defaults that made Rails attractive, while Turbolinks 3, Action Cable, and rails-api help Rails stay useful for both traditional apps and SPAs.
Why I hate your Single Page App
The author argues that most SPAs break core web features, centralize too much behavior in the client, and trade away linking, performance, accessibility, and maintainability for little user benefit.
The Sad State of Web Development
The author argues that modern web development has become over engineered, especially in the Node, frontend, and SPA ecosystems, and says most apps should avoid framework-heavy rewrites.
Little helpers: a tweet-sized JavaScript templating engine
The post argues that for small, short-lived apps and messages, a tiny homemade JavaScript templating helper can be enough, and shows a tweet-sized function that replaces {placeholders}.
Mistakes I Made in My First Ember Project
The author reflects on an early Ember project and says the main problems came from starting before understanding Ember conventions, Ember Data, and the framework’s way of handling state.
Authentication for Single Page Apps
The post argues that single-page app authentication works better when authorization and session creation are modeled as separate API concerns. It presents Torii as an Ember.js abstraction for composable providers, sessions, and adapters.
Developing Backbone.js Applications
A guide to building client-side apps with Backbone.js, covering MVC and MV*, models, views, collections, routers, REST sync, modular development, testing, and common patterns.