DOCSLIB.ORG

Svelte.Js for Modern Front-End Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Svelte.Js for Modern Front-End Development © 2020 JETIR June 2020, Volume 7, Issue 6 www.jetir.org (ISSN-2349-5162) Svelte.js for modern front-end development Vishal1, Dr. Ashwini K. B2 Sixth Semester1, Associate Professor2 Master of Computer Applications RV College of Engineering®, Bangalore, India Abstract These days web applications are used in all sorts of scenarios ranging from Government, Education, Health and Finance etc (1). There are many technical jargons required to create a simple web application, but many frameworks have emerged over the past years to help developers quickly come up with ideas, designs and create complex web interfaces. Although there are many front-end frameworks it is still hard to figure out the coding standards, how the overall build happens and most importantly the performance. Due to this Svelte is an interesting competitor for the front-end market. One of the recently emerging front-end framework is Svelte.js. Svelte is a new approach in building user interfaces. Whereas traditional frameworks like React do the bulk of their work in the browser, Svelte shifts that work into a compile time that happens when you build your app. Which helps developers to create simple code and yet complex web interfaces from scratch, giving more concentration on the design perspective rather than the coding point of view. Keywords Front-end framework, Web application, Svelte.js, Web development, JavaScript. I. INTRODUCTION The past few years of the technological enhancements have grown drastically, improving a big chunk of modern development stages. Web applications have begun from being simple pages that told stories to creating AI integrated intelligent applications that drive our daily life. Front-end development especially has improved a lot due to enhancements in JavaScript itself. This is where Svelte proves to be a tie breaker in the modern front-end development. Svelte not only creates smaller code sections but also helps in understanding the code much easier than any other framework out there. Svelte compiles all the generated files down to a single file (bundle.js). Svelte is a framework, meaning it doesn’t work with the virtual DOM but writes code that surgically updates the DOM when the state of your app changes. The framework was developed by a Rich Harris from The New York Times [9]. To increase the performance of the client-side applications Svelte adopts a build first approach. Which lets the developers build the application which compiles the whole svelte app to a simple build.js file having plain JavaScript. Svelte also improves on the bundling part as the framework itself is 4kb in size. So, the application build file will be very small in size, that is also the reason why using Svelte is faster than any other frameworks. LITERATURE SURVEY JavaScript standards [1] states that ECMAScript 6 (ES6) language standardized the syntax for class and module definitions, streamlining the encapsulation of data and functionality at various levels of granularity. JETIR2006034 Journal of Emerging Technologies and Innovative Research (JETIR) www.jetir.org 206 © 2020 JETIR June 2020, Volume 7, Issue 6 www.jetir.org (ISSN-2349-5162) To know about JIT [2] one popular way of accelerating JavaScript is using the just-in-time compilation (JITC), which translates the JavaScript source code to the machine code at runtime. Evolution of web is described in [3] and states that web browsing is one of the most important applications for personalized consumer electronics devices such as smartphones and tablets. Standards of writing an HTML document [4] states that the recent HTML5 includes, among others, the Web Workers API that allows executing JavaScript applications on multiple threads, or workers. Performance measurement [5] states that web site optimization is divided into front-end optimization and back-end optimization. We found that only 10% - 20% of the time was used to get HTML documents from the Web server to the front-end browsers and the 80% - 90% of the time was used in response to the front end. Performance and load balancing websites [6] states that the increasing demand for faster loading webpages and the need of methods for optimization of the web code in order to increase their speed. Evolution of web [7] is the paradigm that requires architectural changes and that uses models that will increase the flexibility and address the scaling problems in terms of performance, development process and demanding product requirements. Landing page optimization [8] also states that with the development of the Internet, Web applications have become preferred platform of most systems. The whole website has been covered by different regions and more and more pictures, very slow to be opened. II. Working of React Currently the most widely used front end technology is React. A framework developed by Facebook to ease the front-end development process. As the development industry grew wide there were many more frameworks that emerged, say like: Vue.js, Ember and Angular etc. Every framework has their own type of functionality, implementation, approach to coding and build process. Svelte aims to solve all these problems at once by giving a more robust way of providing the overall ecosystem. JETIR2006034 Journal of Emerging Technologies and Innovative Research (JETIR) www.jetir.org 207 © 2020 JETIR June 2020, Volume 7, Issue 6 www.jetir.org (ISSN-2349-5162) Fig.1 React.js lifecycle React uses complex lifecycle methods (as shown in Fig 1) that over time increase the lines of code and eventually hard to maintain. This will also make the work of the developer much more troublesome and increase the amount of time that is invested to build and application. III. React Vs Svelte 1. Svelte is the framework that best meets the API from the web. It puts forth a valiant effort to cling to standard, and just expands on what exists, doesn't concoct anything new like JSX. 2. Alongside point 1, on the grounds that Svelte follows the web's lead, learning Svelte is ludicrously simple. It takes no longer than 5 minutes to grok, and no longer than an hour or so to get completely ready for action. 3. The performance is unshakable - Svelte is regularly demolishing different systems on UI. And it’s increasingly used in production on various popular sites that are in use currently. 4. It's the "vanishing framework." This element is most likely Svelte's most prominent advancement, and each structure should (and many are attempting to) receive it. There are zero customer side conditions. 5. Basic to other unmistakable systems, Svelte authorizes single-record parts to help sort out things. 6. Out-of-the-container checked styles. No compiling reason to ever stress again over tumultuous falling styles. Everything is checked straightforwardly to the part. 7. Smooth trench inheritance programs, yet additionally has a clear way to deal with taking care of heritage, if necessary. JETIR2006034 Journal of Emerging Technologies and Innovative Research (JETIR) www.jetir.org 208 © 2020 JETIR June 2020, Volume 7, Issue 6 www.jetir.org (ISSN-2349-5162) 8. Svelte’s crucial to organize the end client over the engineer. This implies, as referenced above, everything is written in local HTML, CSS, and JavaScript. No peculiar mashups. As far as morals, the normal HTML resident (individuals who are not engineers, yet at the same time need to compose code) can comprehend Svelte. This additionally implies download sizes are greatly diminished in both little and enormous ventures, be that as it may, similarly significant: 9. In view of keeping with existing norms, the designer experience is really surprising. The legos simply fit. 10. Svelte may be the main JavaScript system to caution you when you've missed some availability standard. How? Since it's a compiler, and can do a lot of things that non-compiler structures can't do. IV. Problems with modern frameworks The current situation in the ongoing web application development is very tough as emerging technologies try to compete each other to better outperform each other. Popular way of accelerating JavaScript is using the just-in-time compilation (JITC), which translates the JavaScript source code to the machine code at runtime [2]. Each browser may have their subsequent compilers for the JavaScript to convert it to machine code but the amount of JavaScript itself matters a lot for the performance on the client side. Svelte organises the code in a very neat and organised manner to build and compile Svelte files to pure JavaScript code. This benefits in improved performance and lesser code. This paper does a fine-tuned comparison to an already popular JavaScript framework i.e., React to show the benefits in using Svelte to develop the modern front- end web applications. Fig. 2 Svelte.js lifecycle Fig 2 shows the overall lifecycle of svelte, Svelte has few more important lifecycle methods as follows: JETIR2006034 Journal of Emerging Technologies and Innovative Research (JETIR) www.jetir.org 209 © 2020 JETIR June 2020, Volume 7, Issue 6 www.jetir.org (ISSN-2349-5162) onMount: pursues the segment is first rendered to the DOM. onDestroy: runs when the segment is decimated. beforeUpdate: runs before the DOM has been refreshed. afterUpdate: pursues the DOM has been updated(It's partner of the beforeUpdate). tick: dissimilar to other functions(I'll portray at the last piece of this post) V. How Svelte overcomes these problems Svelte.js provided improved performance when compared to the notorious React.js this is mainly due to the bundling that is done by the svelte’s bundler that converts the “.svelte” files to vanilla JavaScript once the build is completed. Fig.3 Svelte.js bundling the individual components Svelte uses Webpack a famous library that bundles the code to create a more refined html, css and js files.
Load more

Recommended publications
  • Marketing Cloud Published: August 12, 2021
    Marketing Cloud Published: August 12, 2021 The following are notices required by licensors related to distributed components (mobile applications, desktop applications, or other offline components) applicable to the services branded as ExactTarget or Salesforce Marketing Cloud, but excluding those services currently branded as “Radian6,” “Buddy Media,” “Social.com,” “Social Studio,”“iGoDigital,” “Predictive Intelligence,” “Predictive Email,” “Predictive Web,” “Web & Mobile Analytics,” “Web Personalization,” or successor branding, (the “ET Services”), which are provided by salesforce.com, inc. or its affiliate ExactTarget, Inc. (“salesforce.com”): @formatjs/intl-pluralrules Copyright (c) 2019 FormatJS Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    [Show full text]
  • THE FUTURE of SCREENS from James Stanton a Little Bit About Me
    THE FUTURE OF SCREENS From james stanton A little bit about me. Hi I am James (Mckenzie) Stanton Thinker / Designer / Engineer / Director / Executive / Artist / Human / Practitioner / Gardner / Builder / and much more... Born in Essex, United Kingdom and survived a few hair raising moments and learnt digital from the ground up. Ok enough of the pleasantries I have been working in the design field since 1999 from the Falmouth School of Art and onwards to the RCA, and many companies. Ok. less about me and more about what I have seen… Today we are going to cover - SCREENS CONCEPTS - DIGITAL TRANSFORMATION - WHY ASSETS LIBRARIES - CODE LIBRARIES - COST EFFECTIVE SOLUTION FOR IMPLEMENTATION I know, I know, I know. That's all good and well, but what does this all mean to a company like mine? We are about to see a massive change in consumer behavior so let's get ready. DIGITAL TRANSFORMATION AS A USP Getting this correct will change your company forever. DIGITAL TRANSFORMATION USP-01 Digital transformation (DT) – the use of technology to radically improve performance or reach of enterprises – is becoming a hot topic for companies across the globe. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-02 Companies face common pressures from customers, employees and competitors to begin or speed up their digital transformation. However they are transforming at different paces with different results. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-03 Successful digital transformation comes not from implementing new technologies but from transforming your organisation to take advantage of the possibilities that new technologies provide.
    [Show full text]
  • The Jungle Through Javascript Frameworks
    The jungle through Javascript frameworks. Jonatan Karlsson Henrik Ölund Web Programming Web Programming 2013, BTH, Blekinge institute of 2013, BTH, Blekinge institute of technology technology Advanced topic in Web development, PA1426 Advanced topic in Web development, PA1426 HT15 HT15 Karlskrona, Sweden Karlskrona, Sweden [email protected] [email protected] PA1426 Revision C, Advanced topic in Web development 2015-11-05 Abstract In this article we have planned to dive into Javascripts world where new framework comes out “every day”. We will take the reader into a world where nothing are for granted and everything is a non-standard. In the current situation, there is a [3] tremendous amount of Javascript frameworks ​ and that makes it difficult for a ​ layman to choose the right framework, for the right task and this is something we will try figure out and explain to the reader. Keywords: Javascript, Framework, MV*, Client-side, React, Mithril, Backbone.js, ​ Ember.js 1 PA1426 Revision C, Advanced topic in Web development 2015-11-05 Abstract 1. Introduction 1.1 Background 1.2 Intention 1.3 Method First part Does the framework follow the MV*-pattern? Is the framework popular on google? Have the framework risen in popularity since 2013? Does the framework have any corporation that backs them? Second part 2. Result 2.1 Which frameworks did we select? 2.2 Not included 2.3 React What philosophies have pushed this framework forward? What kind of problem does this framework solve? Which famous products has been created with this framework?
    [Show full text]
  • Glen R. Goodwin [email protected] Laurel, Maryland
    Glen R. Goodwin [email protected] Laurel, Maryland https://arei.net Experience August 2019 to Director of Software Engineering / Lead Engineer, Whitebox Technology, Present Baltimore, Maryland • Lead day to day operations of entire Engineering Directorate including growing team from 5 engineers to 18 engineers. • Designed and implemented entire Engineering department’s communication and process and company culture of Software excellence. • Mentored entire team and individual developers in communication, architecture, engineering best practices, and software quality. • Served as Lead Engineer for Systems Team, responsible for implementing innovative systems to deliver faster, more efficently, and at scale • Served as Lead Experience Engineer fostering and implementing consistent cross product common solutions to better enhance the company brand and the end user expereience. • Designed and delivered technical solutions across the entire company on everything from visualizations to automated conveyance systems. July 2018 to Founder, The Awesome Engineering Company, Laurel, Maryland August 2019 • Started The Awesome Engineering Company to productize personally developed open source solutions. • Developed open source products for NodeJS and modern browsers. October 2013 to Distinguished Software Engineer & Chief Architect for CyberSecurity, SAS July 2018 Institute inc, Ellicott City, Maryland • Chief Architect for the SAS Cybersecurity product line overseeing technical (Converted from VSTI vision from inception to release. employee to parent SAS company in October 2013) • Served as Engineering Lead for User Interface, Services (API), Persistence (ElasticSearch), and Enrichment teams structured around technical layers. • Acted as Lead Researcher for new implementations and technology experiments advising senior management on feasibility and direction • Designed and implemented backend and frontend technologies for the entire product from conception to delivery in multiple languages/frameworks.
    [Show full text]
  • From GWT to Angular: an Experiment Report on Migrating a Legacy Web
    From GWT to Angular: An Experiment Report on Migrating a Legacy Web Application Benoit Verhaeghe, Anas Shatnawi, Abderrahmane Seriai, Anne Etien, Nicolas Anquetil, Mustapha Derras, Stephane Ducasse To cite this version: Benoit Verhaeghe, Anas Shatnawi, Abderrahmane Seriai, Anne Etien, Nicolas Anquetil, et al.. From GWT to Angular: An Experiment Report on Migrating a Legacy Web Application. IEEE Software, Institute of Electrical and Electronics Engineers, In press, 10.1109/MS.2021.3101249. hal-03313462 HAL Id: hal-03313462 https://hal.archives-ouvertes.fr/hal-03313462 Submitted on 4 Aug 2021 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Department: Head Editor: Name, xxxx@email From GWT to Angular: An Experiment Report on Migrating a Legacy Web Application B. Verhaeghe Berger-Levrault, France Université de Lille, CNRS, Inria, Centrale Lille, UMR 9189 – CRIStAL, France A. Shatnawi Berger-Levrault, France A. Seriai Berger-Levrault, France A. Etien Université de Lille, CNRS, Inria, Centrale Lille, UMR 9189 – CRIStAL, France N. Anquetil Université de Lille, CNRS, Inria, Centrale Lille, UMR 9189 – CRIStAL, France M. Derras Berger-Levrault, France S. Ducasse Université de Lille, CNRS, Inria, Centrale Lille, UMR 9189 – CRIStAL, France Abstract—Berger-Levrault is an international company that developed applications in GWT for more than 10 years.
    [Show full text]
  • Webpack Cheatsheet
    12/25/18, 655 PM Page 1 of 1 ! Edit Webpack cheatsheet — Proudly sponsored by — Airbrake.io Full-stack error tracking & analytics for Python developers. Try it Free! ethical ads via CodeFund This is a very basic “getting started with Webpack” guide for use with Webpack v3. This doesnʼt cover all features, but it should get you started in understanding the config file format. Basic config webpack.config.js module.exports = { context: __dirname, entry: 'src/app.js', output: { path: __dirname + '/public', filename: 'app.js' } } Terminal npm install --save-dev webpack webpack build webpack -- -p build production webpack -- --watch compile continuously This compiles src/app.js into public/app.js. (Note: you may need to use ./node_modules/.bin/webpack as a command if youʼre not invoking Webpack via npm scripts.) Multiple files webpack.config.js module.exports = { entry: { app: 'src/app.js', vendor: 'src/vendor.js' }, output: { path: __dirname + '/public', filename: '[name].js' } } This creates app.js and vendor.js. # Loaders Babel Terminal npm install --save-dev \ babel-loader \ babel-preset-env \ babel-preset-react webpack.config.js module.exports = { ··· module: { rules: [ { test: /\.js$/, exclude: /node_modules/, use: [ { loader: 'babel-loader' } ] } ] } } .babelrc { "presets": [ "env", "react" ] } Adds support for Babel. CSS Terminal npm install --save-dev \ css-loader \ style-loader webpack.config.js module.exports = { ··· module: { rules: [ { test: /\.css$/, exclude: /node_modules/, use: [ { loader: 'style-loader' }, { loader: 'css-loader'
    [Show full text]
  • State of Frontend 2020 Is the Biggest Report out There Focused Solely on Frontend Development
    1 Experts Yan Cui Tim Neutkens AWS Serverless Hero Head of Next.js at Vercel Marek Gajda Guillermo Rauch CTO of The Software House CEO of Vercel Jessica Jordan Tomek Rudzki Developer Advocate at .cult Head of R&D at Onely Luca Mezzalira Dylan Schiemann VP of Architecture at DAZN CEO of Living Spec Rocky Neurock Bartosz Skowroński Engineering Team Lead Head of Design at Honeypot.io at The Software House 2 Authors Patryk Mamczur Editor in Chief Marcin Gajda Joanna Swoboda Tomasz Kajtoch Magdalena Habarta Wiktor Toporek Kamil Głowiński Andrzej Wysoczański Publication Design Technical Consulting 3 Table of contents Developers 8 01 Everyday frontend development according to 4,500 experts Frameworks 12 02 React is king. But who’s the contender? Hosting 18 03 Traditional DCs, cloud giants and frontend-focused hosting Jamstack 24 04 Ecstatic about static Micro frontends 28 05 Do we need microservice revolution in frontend development? Search engine optimization 32 06 It seems that you don’t care about SEO. Here’s why you should Application accessibility 07 Making the interface friendly for every user 36 4 Development teams 40 08 Frontend development? It’s a team sport Design 44 09 Striving for close collaboration between designers and developers Quality assurance 48 10 Software testing as the cornerstone of software development Future of frontend 52 11 State of Frontend 2021? 5 How many frontend developers took part in the survey? Total answers: 4500 1082 Western Europe 941 North America 333 Central and 6 South America 107 Other 1581 Eastern Europe 1082 Western Europe 303 South and East Asia 73 Middle East 7 01.
    [Show full text]
  • Analysing the Use of Outdated Javascript Libraries on the Web
    Updated in September 2017: Require valid versions for library detection throughout the paper. The vulnerability analysis already did so and remains identical. Modifications in Tables I, III and IV; Figures 4 and 7; Sections III-B, IV-B, IV-C, IV-F and IV-H. Additionally, highlight Ember’s security practices in Section V. Thou Shalt Not Depend on Me: Analysing the Use of Outdated JavaScript Libraries on the Web Tobias Lauinger, Abdelberi Chaabane, Sajjad Arshad, William Robertson, Christo Wilson and Engin Kirda Northeastern University {toby, 3abdou, arshad, wkr, cbw, ek}@ccs.neu.edu Abstract—Web developers routinely rely on third-party Java- scripts or HTML into vulnerable websites via a crafted tag. As Script libraries such as jQuery to enhance the functionality of a result, it is of the utmost importance for websites to manage their sites. However, if not properly maintained, such dependen- library dependencies and, in particular, to update vulnerable cies can create attack vectors allowing a site to be compromised. libraries in a timely fashion. In this paper, we conduct the first comprehensive study of To date, security research has addressed a wide range of client-side JavaScript library usage and the resulting security client-side security issues in websites, including validation [30] implications across the Web. Using data from over 133 k websites, we show that 37 % of them include at least one library with a and XSS ([17], [36]), cross-site request forgery [4], and session known vulnerability; the time lag behind the newest release of fixation [34]. However, the use of vulnerable JavaScript libraries a library is measured in the order of years.
    [Show full text]
  • MASTER THESIS Javascript Frameworks a Qualitative
    MASTER THESIS JavaScript Frameworks A qualitative evaluation and comparison of the dominant factors in Angular and React Abdul Kadir Yorulmaz MSc. in Computer Science & Informatics Supervised by Anders Lassen Department of Computer Science & Informatics June 2, 2020 Abstract The rising number of JavaScript libraries and frameworks that have been developed during the years, gives the experienced and inexperienced practitioners complexity when wanting to commit to a frame- work. Today, a more concrete and analysed evaluation process is lacking for developers in order to make sure a framework fit their needs for the given project’s purpose and size. This thesis explores an evaluation process that can help practitioners determine which framework or library fit their needs for their project, but also choosing the framework that fits best with their experience and preferences when building applications. This study is build on an experiment, where two Todo-list applications were developed via Angular and React. Based on the development process of each application, the framework and library were evaluated via relevant factors that give insights to what to expect from the framework and library in terms of how fast one can learn it, the quality of the documentation, the helpfulness of their communities and the frequency of updates. Through the evaluations, the dominant factors were found for Angular and React, which gave the base for doing the comparative analysis in order to find the differences and similarities between them. By conducting the comparative analysis of the dominant factors within Angular and React, this study gives the indication that Angular gives clear directions when developing and therefore can be well-suited to both experienced developers but also beginners.
    [Show full text]
  • Npm Packages As Ingredients: a Recipe-Based Approach
    npm Packages as Ingredients: a Recipe-based Approach Kyriakos C. Chatzidimitriou, Michail D. Papamichail, Themistoklis Diamantopoulos, Napoleon-Christos Oikonomou, and Andreas L. Symeonidis Electrical and Computer Engineering Dept., Aristotle University of Thessaloniki, Thessaloniki, Greece fkyrcha, mpapamic, thdiaman, [email protected], [email protected] Keywords: Dependency Networks, Software Reuse, JavaScript, npm, node. Abstract: The sharing and growth of open source software packages in the npm JavaScript (JS) ecosystem has been exponential, not only in numbers but also in terms of interconnectivity, to the extend that often the size of de- pendencies has become more than the size of the written code. This reuse-oriented paradigm, often attributed to the lack of a standard library in node and/or in the micropackaging culture of the ecosystem, yields interest- ing insights on the way developers build their packages. In this work we view the dependency network of the npm ecosystem from a “culinary” perspective. We assume that dependencies are the ingredients in a recipe, which corresponds to the produced software package. We employ network analysis and information retrieval techniques in order to capture the dependencies that tend to co-occur in the development of npm packages and identify the communities that have been evolved as the main drivers for npm’s exponential growth. 1 INTRODUCTION Given that dependencies and reusability have be- come very important in today’s software develop- The popularity of JS is constantly increasing, and ment process, npm registry has become a “must” along is increasing the popularity of frameworks for place for developers to share packages, defining code building server (e.g.
    [Show full text]
  • My Story with Webpack
    MY STORY WITH WEBPACK TOBIAS KOPPERS GITHUB: @sokra TWITTER: @wSokra THE STORY FOLLOWED BY “NOW” AND “THE FUTURE” 2008 • STUDIED COMPUTER SCIENCE • JAVA • DISCOVERED GOOGLE WEB TOOLKIT (GWT) • JAVA TO JAVASCRIPT COMPILER • GENERATES BIG JS FILES • BUT ALSO HAD A SOLUTION FOR THIS GWT CODE SPLITTING Button b = new Button("Click me", new ClickHandler() { public void onClick(ClickEvent event) { GWT.runAsync(new RunAsyncCallback() { public void onFailure(Throwable caught) { // ... } public void onSuccess() { Window.alert("Hello world"); } }); } }); 2011 • BACHELOR THESIS • MY FIRST CONTACT WITH OPEN SOURCE • PRESENTATION WITH WEB TECHNOLOGY • JMPRESS.JS: A JQUERY PLUGIN FOR PRESENTATIONS ON A INFINITE CANVAS BY @shama • CONTRIBUTED A LOT, GOT A MAINTAINER • JUST CHECKED IT FOR THIS PRESENTATION: IT’S BROKEN NOW… transition: --transform? • THERE ARE BETTER SOLUTIONS NOW ANYWAY 2012 • MASTER THESIS • PART OF IT WAS A WEB-APPLICATION • NOTE: I LIKE PREMATURE OPTIMIZATION • I WAS LOOKING FOR A “BUNDLER” • I FOUND modules-webmake BY @medikoo • BUT IT WAS LACKING CODE SPLITTING • SO I OPENED AN ISSUE… 2012: ISSUE IN MODULES-WEBMAKE • INITIALLY I PROPOSED TO “ABUSE” process.nextTick FOR CODE SPLITTING • THAT WAS DUMB… • BUT THE IDEA WAS BORN • SOME PEOPLE THOUGHT THIS IS AN USELESS FEATURE • “HOW BIG IS YOUR WEBAPP GOING TO GET?” • WELL ACTUALLY WEBAPPS ARE GOING TO GET VERY BIG THESE DAYS 2012: PROTOTYPE • AFTER SOME DISCUSSION I IMPLEMENTED A PROTOTYPE OF MY IDEA, FROM SCRATCH • IT USES require.ensure FOR CODE SPLITTING • IT ALSO USES NUMERIC IDS,
    [Show full text]
  • Choosing the Right Javascript Framework for Your Next Web
    Choosing the Right JavaScript Framework for Your Next Web Application by Brandon Satrom © 2017 Progress. All Rights Reserved. All Rights © 2017 Progress. 2018 WHITEPAPER Table of Contents The Current State of Web Frameworks / 3 Tooling Considerations / 22 Evaluation Criteria / 5 UI & Component Libraries / 22 Ecosystem Considerations / 7 IDE & Tooling Support / 23 History & Longevity / 7 Companion & CLI Tools / 24 Popularity / 9 Enterprise Considerations / 26 Corporate Support / 11 Licensing / 26 Community & Ecosystem / 12 Support & Upgrade Paths / 27 Framework Considerations / 13 Security / 29 Getting Started Experience / 13 Talent Pool & Resources / 30 Skill Requirements / 15 Making a Choice / 33 Completeness of Offering / 17 Size & Performance / 18 Beyond the Browser Options / 21 © 2018 Progress. All Rights Reserved. All Rights © 2018 Progress. Progress / Kendo UI 2 The state of web application development has changed drastically in the past ten years. These changes have been spurred on by greater bandwidth for many, more powerful and feature-rich browsers. The result is a thriving web ecosystem with sites, apps and experiences that would have been hard to imagine a decade ago. And yet, for many developers, this ecosystem often feels like a bazaar, stuffed with libraries and frameworks that do anything and everything one could imagine. For every need there are a dozen options to choose from, and with new stalls (libraries) opening every day, it’s no wonder many of us pine for the days when starting a new project was as simple as dropping jQuery in a script tag. The Current State of Web Frameworks There’s no doubt that the web has grown in complexity, and our development tooling options have grown along with it.
    [Show full text]