![]() And another solution could be to offer front-end engineers an Abstract Syntax language for front-end development that could be compiled into the syntax of the JavaScript frontend they chose as output.Īll of these could be added to the work that I am doing with this next-generation compiler (also here). Language wrappers that convert C code to Java have already been developed successfully in the past. This would not be hard for a software engineer or a team that masters how compilers are built because all of this is about dealing with grammatical syntax and reserved words. This solution is a wrapper that could take as input the code of a given front-end solution developed with a given JavaScript front-end framework and convert it into the other JavaScript front-end framework syntax and implementation. This second solution highlights a tech-enabled solution that could be useful to low-budget startups and development teams that could not afford many front-end engineers or/and are constrained by time. Or if you’re someone who can master many JavaScript front-end frameworks by yourself, then you need more time to develop the front-end with each framework. But as I have highlighted in this last sentence, this second solution requires many skilled front-end engineers, at least one for each front-end framework. Then you can use the data you have gathered for deciding on what front-end framework your final front-end solution will be based on. The second solution for those who have time and/or human resources is to build your front-end with every popular JS frontend and to do the benchmarking yourself in production. But with such a solution, building trust could be an issue because who knows if I am paid or not by the team behind a JavaScript front-end framework. These benchmarking (benchmarketing is a great name by the way) reports are done by people like me who are independent professionals. One solution could be to gather benchmarking data about each framework and make a choice given that data was gathered. But how do we decide what front-end to choose? ![]() Since jQuery, many frameworks have been created and now front-end engineers can choose from React, Vue.js, Ember.js, AngularJS, Svelte, Inferno, and others for building interactive and creative front-ends that expose the logic and result of their web applications to end-users.Īs I have highlighted in my last article ( here) about JavaScript frameworks and core web vitals metric, the choice of JavaScript front-end framework does not depend on the front-end engineer’s skills and will but on the values that are delivered to the end-users - and the time the application takes to show content to the user is becoming on of the most important values. JavaScript front-end frameworks are now very popular and useful to all the community of JavaScript developers. Image with the logo of most popular Javascript frontend frameworks by mindinventory ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |