A tale of the last 10 years in web development

This is a work of fiction. Names, characters, businesses, places, events, locales, and incidents depicted in this story are either the products of my imagination or used in a fictitious manner. Any resemblance to actual persons, living or dead, or actual events is purely coincidental.

An Introduction

This story is based on a true story of each of us. Over the past 10 years, many web developers have experienced such a journey. Starting from jQuery, passing through Angular, using React and streak Vue.

https://github.com/adrai/i18next-main-differentiator/tree/master/jquery
https://github.com/adrai/i18next-main-differentiator/tree/master/angular

“Is this still Angular?”

In the meantime, the backend had turned into a solid foundation based on DDD, CQRS and event sourcing.
During a late-night beer, Dorian told Shaun about React and Redux. He said that when he read about React, Redux and FLUX he immediately felt that this was a natural fit to the existing backend.
Finally, they convinced Patty to rewrite the whole frontend with these arguments:

https://blog.gisspan.com
  • the more flexible state management with Redux
  • virtual DOM, one-way data flow, PropTypes and a well-defined component lifecycle
  • the obvious natural fit with their backend
  • single source of truth
  • JSX, a natural evolution of Javascript
  • React has faster learning curve. It feels like learning faster.
https://github.com/adrai/i18next-main-differentiator/tree/master/react

React is ok, but what’s about Vue?”

Shaun and Dorian organized a little technical session and they explained that React and Vue had more similarities than differences:

  • both had a component based architecture
  • both used a virtual DOM
  • both could be dropped into a single HTML file or be a module in a more sophisticated webpack setup
  • both had separate router and state management libraries

“Ok, let’s try to write our web app in Vue and create a PoC…”

Whether they’ve really switched to Vue, we do not know, but what we know is that if that’s the case, then they’re sure to use vue-i18next or a similar library.

https://github.com/adrai/i18next-main-differentiator/tree/master/vue

“learn once — translate everywhere”!

Technologies and libraries come and go, but i18next remains!

Post-credits scene

There are voices who say that they have also replaced their i18next-xhr-backend with that of locize.

founder of locize.com; Software Architect, Bachelor in Computer Science #serverless #nodejs #cqrs #ddd always in search for #innovative and #disruptive stuff