A common optimization would be to preload the served javascript with the initial AJAX results. This still means rendering the content on the client side, but the content isn't fetched asynchronously. Another optimization is to actually render all the DOM elements in advance on the server, and only use client side rendering for updates.
Which is, you know, how the web is supposed to work.
The problem is it's still quite raw and full of demo-stuff. Not in the way it loads.
Although... yes, isn't Angular a bit overkill here?
For me, the most important part is the language. I can use JavaScript for client side, server side, and database. There is no context switching related to language like Ruby, JavaScript, SQL. (And, the way of thinking related to that like asynchronous and synchronous.)
It is especially helpful for startup or prototyping where small team build everything.
No seriously, the askbot guys have been for a long time on the field, great app.
Building a Q&A web service in an hour - MEAN stack development(3) http://engineering.paiza.io/entry/2016/03/10/115345
Also, there was a issue on Social Login, I also fixed the issue.
<navbar></navbar>
Do you even know that this is invalid and the proper tag is called just <nav>? Do you know that <title> must not be empty in the initial page? Do you know that custom attributes must start with data- (not ng- or ui-)?
Did you even check your page with http://validator.w3.org?
I honestly don't understand how did the authors manage to make a skeleton (!) page not passing validation. Even <title> is empty when it must not be so.
Is it because of Angular? Well, if a framework forces you to write invalid HTML (tags, attributes, whatever), it sucks, no matter what.
Building a QA web service in an hour - MEAN stack development(3)
I even wrote a rails console-like equivalent for the older version[1]. Didn't get time to write a new one though. Will be a good addition to the generator I think.
http://paizaqa.herokuapp.com/questions/show/56e1a5872c8dfa03...
