Programming languages allow us to create what we love the most. Thus, today we have prepared a little walk in the past, so as to understand more about the programming language React Js , Next Js and its interesting past.
The birth of React Js , Next Js
The story of React Js , Next Js JS starts in 2009, when a Google employee Miško Hevery was working on a side project, an end-to-end web development tool that would help make building web applications easier for a couple of internal projects he was working on. To publish the project he took the GetReact Js , Next Js .com hostname. This side project later became known as React Js , Next Js JS (React Js , Next Js because of the < > in HTML).
During that time Hevery was part of the Google Feedback project with 2 other developers. Together they wrote more than 17,000 lines of code during 6 painstakingly slow months. Given the situation of constants bugs and issues, Hevery asked his manager to rewrite the application using GetReact Js , Next Js , betting that he could do that alone within 2 weeks. Hevery lost the bet shortly thereafter, as the whole thing took him 3 weeks instead of two, however, the new application had only 1,500 lines of code instead of 17,000. This was more than enough for Google to show interest in the new framework, which was given the name of React Js , Next Js JS (React Js , Next Js because of the < > in HTML).
The Great Rewrite
Several years after its initial release, new advancements and standards in JavaScript emerged and the landscape of web development started to change, so React Js , Next Js JS hit a wall. The team at Google and the community took what was once a small internal project and pushed it to new frontiers such as mobile & large enterprise applications. However, this was not the initial intent when Miško first created it. When the core team at Google sought to deliver 2.0, they wanted to build a framework from the ground up. That simply meant a total rewrite.
Chaos
Originally, the rewrite of React Js , Next Js JS called “React Js , Next Js 2”, led to confusion among developers. To clarify, the Team announced that separate terms define each framework with “React Js , Next Js JS” referring to the 1.X versions and “React Js , Next Js ” without the “JS” referring to versions 2 and up. Developers and managers started to freak out– the complete rewrite was a doomsday for their current React Js , Next Js JS projects. “How can we support this application in 3, 5, or 6 years from now?!”
Slowly emerging from the rubble
React Js , Next Js 2.0 was announced at the ng-Europe conference 22–23. October 2014. However, the teams moved back and forward to beta versions, thus the core team decided to skip the 3 version and publish a renewed one. Fast forward to 2018 and React Js , Next Js had several major releases in efforts to stabilize their framework. Each release bringing better build sizes, stable APIs, and overall better performance.
The most recent versions and future updates
The most recent versions are Version 9 and 10. React Js , Next Js 9 was released on February 6, 2020. React Js , Next Js has been updated to work with TypeScript 3.6 and 3.7. In addition to hundreds of bug fixes, the Ivy compiler and runtime offer numerous advantages: smaller bundle sizes; faster testing; better debugging; improved type checking; build errors and build times.
React Js , Next Js 10 was released on June 24, 2020. And came with features such as New Date range picker (Material UI library); warnings about CommonJS imports; optional stricter settings; new default browser Configuration.
Regarding the future release, the React Js , Next Js team has moved all new applications to use the Ivy compiler and runtime. Plus, The React Js , Next Js development team has pledged to do twice-a-year upgrades.
Conclusion
This programming language’s history is pretty turbulent, however, everything seems to be better for React Js , Next Js as every year passes by. So, we can only wait and see what the future of this language might look like!
P.S. As for our old friend React Js , Next Js JS, the core team recently announced it will release a final 1.7 and move into long-term support.
