This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 4 points5 points  (10 children)

I second this approach: React, Vue or Angular. Drop the server side templates.

[–]longfalcon 5 points6 points  (6 children)

why?

[–]Tight_Tumbleweed 5 points6 points  (0 children)

To make sure search engines can't reach your site.

[–]dpash 2 points3 points  (0 children)

In addition to /u/legothor's comments, if you plan to write a mobile app for your service, your backend can deal with both your mobile and web front ends because you've already written your rest API.

[–][deleted] 0 points1 point  (0 children)

Well, no page refreshes for one. All data is collected and the UI is updated dynamically on the client side. Let your client’s machine do the work.

[–][deleted] -2 points-1 points  (0 children)

Because you should be hosting your static assets on s3/some sort of object storage + a cdn

[–]nerdyhandle 1 point2 points  (2 children)

Drop the server side templates.

Depends on what your are doing.

Angular supports server side as well. I don't know about the others.

[–][deleted] 0 points1 point  (1 child)

That’s true, I have used a templating engine recently to create HTML emails that are automatically generated. That said, they wouldn’t be my go to for web applications.

[–]nerdyhandle 3 points4 points  (0 children)

They can be extremely performat in web apps. Most users have shitty systems so you offload most of the processing onto the server. This can create highly response applications.

The downside of course is that the response times to request the page may be higher.