Earlier quoted context omitted.
>It may seem old-fashioned but when I load a web page I don't want to sit looking at a 'loading' message or a progress bar This is how bad implementations look to users, consider something like Gmail as a counter example however... >would be interesting to hear the reasons behind the string of assertions in your penultimate sentence Sure:) >are you sure all types of app would benefit equally from your approach? Of co…
Thanks for the comments, it'd be easier to read if they weren't styled using pre! Of course I am not, I didn't make a that claim. Sorry, I should have phrased that differently as something like - perhaps not all types of app would benefit equally? I wasn't trying to put words in your mouth. I do think it's a little early to start asking why anyone would use server-side logic any more, there is room for both approache…
>though it is possible to have a back-end behind a traditional web framework too.
Sure I think you get a lot of the maintainability pro's this way, but loose on some of the performance ones.
I mostly write systems software (in Go), but when I write webapps I use angular.js (frontend) + Go (backend) + One of many datastores (ex MySQL, Postgre, LevelDB etc)