News for hackers. Stuff that matters.
Re:Hacker News written with Angular 2.0 by pdkl95 on Sunday April 19, 2015 @08:14PM (#9405450)
Seems to be serving a broken page...

    <div class="bodyContainer">
      <hacker-news></hacker-news>
    </div>
Re:Hacker News written with Angular 2.0 by iovar on Sunday April 19, 2015 @08:25PM (#9405484)
That's the body before any javascript runs.

Did you really open a link about an angularjs project, with javascript disabled, just to be able to say it's broken?

Re:Hacker News written with Angular 2.0 by hswolff on Sunday April 19, 2015 @08:24PM (#9405479)
author here, Are you still seeing that? Can you open an issue with further details please?
Re:Hacker News written with Angular 2.0 by pdkl95 on Sunday April 19, 2015 @08:57PM (#9405584)
It is a mistake to assume a browser supports javascript.

Angular/meteor/etc do not generate sane output, as throwing up what is essentially an empty body tag (literally so, in some cases) is not only totally unusable outside the one use-case you have planned for, the page being generated is equivalent to a server error.

The correct solution, of course, is to render the page server side (and cache it, if you're sane), and progressively enhance any features such as XHR-style loading. Some comments later in this thread have mentioned that this might be an upcoming feature in the near future, which is great.

Without server-side rendering? That is still no excuse to serve up an empty page. Put some sort of fallback there, or a link to some alternative page. At a minimum, at least have a proper error message about how your site only only works in browsers that support javascript.

Re:Hacker News written with Angular 2.0 by djm_ on Sunday April 19, 2015 @09:19PM (#9405644)
> It is a mistake to assume a browser supports javascript.

I really feel at this stage in the battle that that argument is hurting the call for server side rendering. Don't get me wrong, I have been a pusher for PE for many years but it quite clearly is falling on deaf ears these days.

The reason being is that it's very easy for someone to turn around and say "none of our users that we care about turn js off". However it is much harder to ignore the fact that initial page load times with server side rendering are minimal in comparison to the render-via-js frameworks of today.

I believe we need to follow the performance argument.