News for hackers. Stuff that matters.
Re:Regressive Web Apps by pdkl95 on Wednesday May 25, 2016 @03:44PM (#11772506)
> rendering front ends with javascript shouldn't be considered breaking the web.

If you want to serve an empty, broken page as a first impression, you can. I strongly recommend against it because it makes your site look half-finished, poorly designed, and generally unprofessional.

> available in the browser

That isn't always true. You don't know anything about the browser a priori.

> make a better experience

Of course. Javascript can add nice features, which is why you progressively enhance the page to add features when the underlying requirements are available. Do you skip the check for NULL when calling fopen(1)? Checking for errors is always important. On the web, this means you should gracefully handle problems like missing javascript (intentionally or otherwise) or other resources.

> Making UIs respond faster

Requiring two additional HTTP requests (one to load javascript, and another to load the actual page content) isn't making the page faster. After the first request your javascript will be available most of the time for partial loads in any case.

> interactive content

That is rarely a good idea, but it's your page so do what you want. Progressive enhancement doesn't affect this at all.

Re:Regressive Web Apps by agmcleod on Wednesday June 01, 2016 @03:45PM (#11817535)
I think you and I are talking about the same thing. I was more responding to the extreme circumstances the other person posted. I agree that when you're making public facing content, it should render on the server. The faster UIs is true when you don't have to do full page reloads to load new content, but just grab serialized data from the web server instead.
Re:Regressive Web Apps by random_rr on Wednesday May 25, 2016 @04:25PM (#11772780)
Do you develop, professionally, for the web?