One of the best known mottos around the web is Java’s
How We Arrived Here
As the years have passed, the responsibilities of the client-side code have grown a lot, resulting in a new type of application known as the single-page application (SPA). In an SPA, all the necessary assets are retrieved with a single page load, or dynamically loaded and added to the page as necessary. Some examples of SPAs are Gmail and the StackEdit editor.
SPAs allow for better interactivity, because almost all their operations are executed on the client, keeping communications with the server to a bare minimum. Unfortunately, they also have some major problems. Let’s discuss some of them.
Because SPAs require more client-side code than static pages, the amount of data to download is increased. This leads to slower initial loading times, which can have drastic consequences – such as frustrated end users and loss of revenue. According to one Microsoft article –
A Bing study found that a 10ms increase in page load time costs the site $250K in revenue annually.
More companies are adopting Node.js for their products. Sharing code between the client and server is becoming a more common and natural choice, and in my opinion is the future of web development. This trend is enhanced by sharing templates through libraries like React.
Using Redis with Node.js
By Ivaylo Gerchev,
Need fast data interactions in your Node app? Learn how Redis speeds caching, message brokering, sessions, analytics, streaming and more.
By Rui Sousa,
You can now extend the Notion app with the new Notion API. Learn how to create an interface that connects Notion to an external database.
Build a Website with React and Tailwind CSS
By Shahed Nasser,
React and Tailwind CSS: a beautiful relationship! Learn how Tailwind frees you from writing CSS so you can focus on your React components.