Cliff Clavin is hiding in the tall grass.
Hotel room coffee. Looks like real coffee. Smells like real coffee. Is not real coffee.
First step’s a doozy
Eleanor’s post-walk pocket treasures
I’m glad to see Rails supporting multiple architectures. The stuff they’re adding into Rails 5 will give developers a lot more flexibility when it comes time to build a front-end for their application (or multiple front-ends for apps that need separate web and mobile apps). That’s a good thing.
I took issue with this, though:
But if you’re a “prepper” (to borrow a term from DHH’s
In my roughly 20 years of web development, I’ve never had a client say to me, “You know what our app really needs? Fast client-side routing.” Nor have I had any who were interested in providing a web-based interface that matched a native client in terms of features. When clients want native performance, they get a native app. And they understand the limitations of a web-based interface.
Supporting multiple clients, though, is absolutely worth thinking about if that’s what your users need. Rails 5 is going to make these architecture decisions easier, and that’s pretty exciting.