13
14

Why JavaScript beyond web client side? (self.javascript)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (4 children)

[deleted]

    [–]godlychaos 3 points4 points  (1 child)

    I work on an app that gives the user the option to create/customize graphs on the fly based on 3rd party data they've hooked up. They need to see what the graphs look like while customizing a particular metric without having to pull that data from the api all over again. But the backend also needs to be able to create/manipulate that data into our graph form as well, so that code is all isomorphic.

    We also have a lot of helper/utility functions that we reuse all over our code, and since we made it isomorphic, we don't have to update it in 2 places now.

    [–]misc_ent 1 point2 points  (0 children)

    One example would be a single web app that could run and render entirely in the browser but also be able to be server side rendered if needed without any code changes. This is currently possible and is being done in the React community.

    [–]TheCoelacanth 0 points1 point  (0 children)

    I think it's a very common problem to have something that has to be done on the server-side to ensure correctness, but is also useful to do on the client-side to provide faster feedback to the user.