Calling Developers!
We are reenergizing our code contribution process! Learn More

What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

> *Couldn’t We Just Have One API?* > Yes, we could. Such as we could have a backend rendering

Options
Chemaclass
Chemaclass Tech Lead Spryker Solution Partner Posts: 213 🧑🏻‍🚀 - Cadet

Couldn’t We Just Have One API?
Yes, we could. Such as we could have a backend rendering the HTML and no fancy react.
Similarly, we can keep CSS next to HTML.

https://dev.to/fulopattila122/rest-apis-vs-backend-for-frontend-4hba

Comments

  • U01T075RRHD
    U01T075RRHD Posts: 118 🧑🏻‍🚀 - Cadet
    Options

    Nice read, thanks for sharing.
    I don't fully agree on HTML being solely a UI thing, though. For a long time HTML has been consumed by machines (search engine bots) and analyzed for its semantics.

  • U01T075RRHD
    U01T075RRHD Posts: 118 🧑🏻‍🚀 - Cadet
    edited June 2021
    Options

    And more recently, with single page applications, we have so called server side rendering to produce HTML for search engine bots because they will not consume the - mostly proprietary - JSON data