I suspect that, more and more, people are going to realize that they can get a huge amount of utility–and decreased maintenance burden–by simplifying their pages in this fashion.
If you have a backend that’s worth a damn it only takes a little JS to make a page awesome.
Indeed, I think DHH’s argument of pushing things to the client only when absolutely necessary (as is done with Basecamp, for example) makes a lot of sense.
That, unfortunately, is the sticking point for many projects.
There is so much more excitement that comes with working with the newest in-browser tech, because a rewrite or a new take on an old project always feels so hopeful. Meanwhile, back-end languages and tools feel like they’ve stayed the same (even though they haven’t). Thus the idea of an appropriately-architected back-end built with disciplined practices gets less attention from teams of the hype-driven development mindset.
This is one thing that gives me hope for Elixir: It’s a wolf in sheep’s clothing for reliable back-end architectures. It feels new, but is really 80% old, proven best practices. We just need enough people who see and appreciate that aspect to keep the community focused on it, rather than succumbing to runaway novelty-cum-excitement.
I suspect that, more and more, people are going to realize that they can get a huge amount of utility–and decreased maintenance burden–by simplifying their pages in this fashion.
If you have a backend that’s worth a damn it only takes a little JS to make a page awesome.
Indeed, I think DHH’s argument of pushing things to the client only when absolutely necessary (as is done with Basecamp, for example) makes a lot of sense.
That, unfortunately, is the sticking point for many projects.
There is so much more excitement that comes with working with the newest in-browser tech, because a rewrite or a new take on an old project always feels so hopeful. Meanwhile, back-end languages and tools feel like they’ve stayed the same (even though they haven’t). Thus the idea of an appropriately-architected back-end built with disciplined practices gets less attention from teams of the hype-driven development mindset.
This is one thing that gives me hope for Elixir: It’s a wolf in sheep’s clothing for reliable back-end architectures. It feels new, but is really 80% old, proven best practices. We just need enough people who see and appreciate that aspect to keep the community focused on it, rather than succumbing to runaway novelty-cum-excitement.