4 ms·
I would like to see a version for REST and SPAs as well
by wolfi1 9y ago
I would like to see a version for REST and SPAs as well
- e12e 9y agoAgreed! It's great that the book is published under an open license - my first thought was that it'd be fun to port this to f# - and my second thought was to restructure it a bit, focusing on REST/SPA. Having read through it, it is indeed nice and concise - but I'm of two minds of the content - is it really good to introduce server side rendering with jquery and ajax - today? I think, that showing server side rendering is good, for a beginner (how do I go from a form, to db, and back to a simple html table?) - but I'm not sure how useful the "half-way to smart client"-approach of jquery is. I'm almost convinced throwing out most of the server side rendering in favour of returning json and rendering everything client side would be better, than the "in between" approach. Now you have rendering and interaction spread over server side views and client side javascript - and I'm not sure I like the path it sets up for new developers. But for someone that "grew up" with the html to html+ajax it made the book very accessible, and manages to show off a remarkably broad and (apparently) useful section of asp.net core to someone not well versed in asp.net core.
- nbarbettini 9y agoVery good points, thanks. I struggled with this myself as I was trying to plan out the structure of the book. I ultimately went with the "path of least resistance" (ASP.NET Core MVC ships with Bootstrap, jQuery, etc) but I agree that it could be better in future versions. :)