Type-Level Computations for Ruby Libraries

Total Page:16

File Type:pdf, Size:1020Kb

Type-Level Computations for Ruby Libraries Type-Level Computations for Ruby Libraries Milod Kazerounian Sankha Narayan Guria Niki Vazou University of Maryland University of Maryland IMDEA Software Institute College Park, Maryland, USA College Park, Maryland, USA Madrid, Spain [email protected] [email protected] [email protected] Jeffrey S. Foster David Van Horn Tufts University University of Maryland Medford, Massachusetts, USA College Park, Maryland, USA [email protected] [email protected] Abstract types depend on values. Yet this case occurs surprisingly Many researchers have explored ways to bring static typing often, especially in Ruby libraries. For example, consider the to dynamic languages. However, to date, such systems are following database query, written for a hypothetical Ruby not precise enough when types depend on values, which on Rails (a web framework, called Rails henceforth) app: often arises when using certain Ruby libraries. For example, Person.joins (:apartments).where ({ name: ' Alice ' , age: 30, the type safety of a database query in Ruby on Rails depends apartments: {bedrooms: 2}}) on the table and column names used in the query. To address This query uses the ActiveRecord DSL to join two database this issue, we introduce CompRDL, a type system for Ruby tables, people1 and apartments, and then filter on the values that allows library method type signatures to include type- of various columns (name, age, bedrooms) in the result. level computations (or comp types for short). Combined with We would like to type check such code, e.g., to ensure singleton types for table and column names, comp types let the columns exist and the values being matched are of the us give database query methods type signatures that com- right types. But we face an important problem: what type pute a table’s schema to yield very precise type information. signature do we give joins? Its return type—which should Comp types for hash, array, and string libraries can also in- describe the joined table—depends on the value of its argu- crease precision and thereby reduce the need for type casts. ment. Moreover, for n tables, there are n2 ways to join two We formalize CompRDL and prove its type system sound. of them, n3 ways to join three of them, etc. Enumerating all Rather than type check the bodies of library methods with these combinations is impractical. comp types—those methods may include native code or be To address this problem, in this paper we introduce Comp- complex—CompRDL inserts run-time checks to ensure li- RDL, which extends RDL [18], a Ruby type system, to include brary methods abide by their computed types. We evaluated method types with type-level computations, henceforth re- CompRDL by writing annotations with type-level computa- ferred to as comp types. More specifically, in CompRDL we tions for several Ruby core libraries and database query APIs. can annotate library methods with type signatures in which We then used those annotations to type check two popular Ruby expressions can appear as types. During type check- Ruby libraries and four Ruby on Rails web apps. We found ing, those expressions are evaluated to produce the actual the annotations were relatively compact and could success- type signature, and then typing proceeds as usual. For ex- fully type check 132 methods across our subject programs. ample, for the call to Person.joins, by using a singleton type Moreover, the use of type-level computations allowed us for :apartments, a type-level computation can look up the arXiv:1904.03521v1 [cs.PL] 6 Apr 2019 to check more expressive properties, with fewer manually database schemas for the receiver and argument and then inserted casts, than was possible without type-level com- construct an appropriate return type.2 putations. In the process, we found two type errors and a Moreover, the same type signature can work for any model documentation error that were confirmed by the developers. class and any combination of joins. And, because CompRDL Thus, we believe CompRDL is an important step forward in allows arbitrary computation in types, CompRDL type sig- bringing precise static type checking to dynamic languages. natures have access to the full, highly dynamic Ruby envi- ronment. This allows us to provide very precise types for the Keywords type-level computations, dynamic languages, large set of Rails database query methods. It also lets us give types, Ruby, libraries, database queries precise types to methods of finite hash types (heterogeneous hashes), tuple types (heterogeneous arrays), and const string 1 Introduction 1Rails knows the plural of person is people. There is a large body of research on adding static typing 2The use of type-level computations and singleton types could be considered to dynamic languages [2–4, 21, 28, 36, 37, 42–44]. However, dependent typing, but as our type system is much more restricted we existing systems have limited support for the case when introduce new terminology to avoid confusion (see § 2.4 for discussion). types (immutable strings), which can help eliminate type type checking these benchmarks required 4.75× fewer type casts that would otherwise be required. cast annotations compared to standard types, demonstrating Note that in all these cases, we apply comp types to library comp types’ increased precision. (§5 contains the results of methods whose bodies we do not type check, in part to avoid our evaluation.) complex, potentially undecidable reasoning about whether Our results suggest that using type-level computations a method body matches a comp type, but more practically provides a powerful, practical, and precise way to statically because those library methods are either implemented in type check code written in dynamic languages. native code (hashes, arrays, strings) or are complex (database queries). This design choice makes CompRDL a particularly 2 Overview practical system which we can apply to real-world programs. The starting point for our work is RDL [18], a system for To maintain soundness, we insert dynamic checks to ensure adding type checking and contracts to Ruby programs. RDL’s that these methods abide by their computed types at runtime. type system is notable because type checking statically an- (§2 gives an overview of typing in CompRDL.) alyzes source code, but it does so at runtime. For example, C We introduce λ , a core, object-oriented language that for- line6 in Figure 1a gives a type signature for the method C malizes CompRDL type checking. In λ , library methods can defined on the subsequent line. This “annotation” is actu- be declared with signatures of the form ¹a<:e1/A1º ! e2/A2, ally a call to the method type,3 which stores the type signa- where A1 and A2 are the conventional (likely overapproxi- ture in a global table. The type annotation includes a label mate) argument and return types of the method. The precise :model. (In Ruby, strings prefixed by colon are symbols, which argument and return types are determined by evaluating are interned strings.) When the program subsequently calls e1 and e2, respectively, and that evaluation may refer to the RDL.do_typecheck :model (not shown), RDL will type check C type of the receiver and the type a of the argument. λ also the source code of all methods whose type annotations are performs type checking on e1 and e2, to ensure they do not go labeled :model. C wrong. To avoid potential infinite recursion, λ does not use This design enables RDL to support the metaprogramming type-level computations during this type checking process, that is common in Ruby and ubiquitous in Rails. For exam- instead using the conventional types for library methods. Fi- ple, the programmer can perform type checking after meta- C nally, λ includes a rewriting step to insert dynamic checks programming code has run, when corresponding type defini- to ensure library methods abide by their computed types. We tions are available. See Ren and Foster [36] for more details. C prove λ ’s type system is sound. (See §3 for our formalism.) We note that while CompRDL benefits from this runtime We implemented CompRDL on top of RDL, an existing type checking approach—we use RDL’s representation of Ruby type checker. Since CompRDL can include type-level types in our CompRDL signatures, and our subject programs computation that relies on mutable values, CompRDL inserts include Rails apps—there is nothing specific in the design of additional runtime checks to ensure such computations eval- comp types that relies on it, and one could implement comp uate to the same result at method call time as they did at type types in a fully static system. checking time. Additionally, CompRDL uses a lightweight analysis to check that type-level computations (and thus type 2.1 Typing Ruby Database Queries checking) terminate. The termination analysis uses purity While RDL’s type system is powerful enough to type check effects to check that calls that invoke iterator methods—the Rails apps in general, it is actually very imprecise when main source of looping in Ruby, in our experience—do not reasoning about database (DB) queries. For example, consider mutate the receiver, which could introduce non-termination. Figure 1a, which shows some code from the Discourse app. Finally, we found that several kinds of comp types we devel- Among others, this app uses two tables, users and emails, oped needed to include weak type updates to handle muta- whose schemas are shown on lines2 and3. Each user has an tion in Ruby programs. (§4 describes our implementation in id, a username, and a flag indicating whether the account more detail.) was staged. Such staged accounts were created automatically We evaluated CompRDL by first using it to write type by Discourse and can be claimed by the email address owner.
Recommended publications
  • 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]
  • Enough Documentation Release 2.1.22
    Enough Documentation Release 2.1.22 Enough Community Sep 11, 2021 Infrastructure guide 1 Introduction 3 1.1 Requirements...............................................3 1.2 Quick start................................................4 2 Using Enough 5 2.1 Knowledge................................................5 2.2 Using the cloud or physical machines..................................5 2.3 Installation of the Enough CLI......................................5 2.4 Upgrade.................................................6 2.5 OpenStack Enough instance.......................................6 2.6 libvirt Enough instance..........................................7 2.7 Connecting libvirt and OpenStack Enough instances..........................8 2.8 Create or update a service........................................9 2.9 Restore a service............................................. 10 2.10 OpenStack infrastructure services and access.............................. 10 2.11 Certificates................................................ 11 2.12 OpenStack Attached volumes...................................... 12 2.13 Background tasks............................................. 13 2.14 Access.................................................. 13 2.15 OpenStack backups........................................... 13 2.16 Low level commands........................................... 15 3 Services 17 3.1 Nextcloud................................................ 17 3.2 Forum.................................................. 17 3.3 Mattermost...............................................
    [Show full text]
  • Linking Platforms, Practices, and Developer Ethics: Levers for Privacy Discourse in Mobile Application Development
    J Bus Ethics DOI 10.1007/s10551-017-3504-8 ORIGINAL PAPER Linking Platforms, Practices, and Developer Ethics: Levers for Privacy Discourse in Mobile Application Development 1 2 Katie Shilton • Daniel Greene Received: 10 August 2016 / Accepted: 7 March 2017 Ó The Author(s) 2017. This article is an open access publication Abstract Privacy is a critical challenge for corporate managers who wish to promote ethical practices in mobile social responsibility in the mobile device ecosystem. development. Mobile application firms can collect granular and largely unregulated data about their consumers, and must make Keywords Corporate social responsibility Á Occupational ethical decisions about how and whether to collect, store, ethics Á Privacy Á Qualitative analysis Á Technology ethics and share these data. This paper conducts a discourse analysis of mobile application developer forums to dis- cover when and how privacy conversations, as a repre- Introduction: Investigating Work Dynamics sentative of larger ethical debates, arise during that Impact Privacy Reflection development. It finds that online forums can be useful spaces for ethical deliberations, as developers use these Mobile technologies enable new forms of access to infor- spaces to define, discuss, and justify their values. It also mation and communication. But even as the capabilities of discovers that ethical discussions in mobile development mobile technologies advance, many fail to reflect and are prompted by work practices which vary considerably support the values of their users. Studies demonstrate a between iOS and Android, today’s two major mobile striking discord between user values such as privacy and platforms. For educators, regulators, and managers inter- implementation of these values in mobile technologies ested in encouraging more ethical discussion and deliber- (Martin and Shilton 2015).
    [Show full text]
  • Gradual Write-Barrier Insertion Into a Ruby Interpreter
    Gradual Write-Barrier Insertion into a Ruby Interpreter Koichi Sasada Cookpad Inc. Japan [email protected] Abstract older generation objects (old objects) to younger generation Ruby is a popular object-oriented programming language, objects (young objects) [2, 6]. If we forget to insert even one and the performance of the Ruby garbage collector (GC) di- WB, the young objects may be wrongly collected. Of course, rectly affects the execution time of Ruby programs. Ruby2.0 this would be a critical GC bug. and earlier versions employed an inefficient non-generational If you need to implement a generational GC on an inter- conservative mark-and-sweep GC. To improve this and make preter which does not have WBs yet, how can you implement it a generational collector, it is necessary to introduce write it? One straightforward approach is to completely introduce barriers (WBs), but this requires huge modification to exist- all WBs at once. However, if you cannot modify parts of the ing source code, including third-party C-extensions. To avoid source code writing to objects (e.g., in C-extensions), it is the need for adding WBs around legacy code, we invented a not possible to add all required WBs. new concept called “WB-unprotected objects”, which indi- This was the case for the Ruby interpreter in 2013 and cates to the GC to treat such objects more conservatively. By before. leveraging this design, we were able to improve the perfor- The Ruby object-oriented programming language [4] is mance of Ruby 2.1 with a generational GC and of Ruby 2.2 used worldwide, especially for web application development with an incremental GC while preserving compatibility with with the Ruby on Rails framework [11].
    [Show full text]
  • Discord Music Bot Bad Request
    Discord Music Bot Bad Request MishnaicGuido consult Gabriel creditably. denounces Marc gnostically remains cultured and purblindly. after Tony autolyze well or rotes any riempie. Tremain usually infuriate eighth or revalidated groggily when This comes into discord music bot Botisimo Chatbot & Streamer Tools for Twitch YouTube. We never went through an odd idea but exercise, Built for Developers. To discord bot will mean for gamers and then attempt to malformed syntax. Keep your discord music bots that add localized video that. They were capable of sending stickers videos music locations documents and. 10 Best Discord Music Bots You business Use 2020 Beebom. Show you generate a bot in nature or swaying trees. Skype is deserve of salt high-definition video calls HD calls have clear video quality the audio is in sync and the experience is void as with you're bean in front bench the other person for full-HD Skype calls have some technical requirements. How to record better audio on only phone Popular Science. An automated processes, discord bots is arguably one request? It even when people on discord bot is bad video could not request has a way. But became really shouldn't cause that is one kiss Sends a gif of a fresh for mentioned. How discord bot user requests that have any comments cannot be patience for discord bot! Hydra lets you with critical reviews and not make the discord bot that monitor will code looks like top music, atom a token for membership and make the discord. Block this does not support the requester.
    [Show full text]
  • The E-Government Development Discourse
    The e-Government Development Discourse Analysing Contemporary and Future Growth Prospects in Developing and Emerging Economies Kelvin J. Bwalya The e-Government Development Discourse Analysing Contemporary and Future Growth Prospects in Developing and Emerging Economies Published by AOSIS (Pty) Ltd, 15 Oxford Street, Durbanville 7550, Cape Town, South Africa Postnet Suite #110, Private Bag X19, Durbanville 7551, South Africa Tel: +27 21 975 2602 Fax: +27 21 975 4635 Email: [email protected] Website: https://www.aosis.co.za Copyright © Kelvin J. Bwalya. Licensee: AOSIS (Pty) Ltd The moral right of the author has been asserted. Cover: Original design created with the use of images released under the CCO Creative Commons license. The images are https://pixabay.com/en/analytics-information- innovation-3088958/ and https://pixabay.com/en/cape-town-south-africa-historically-997524/. ISBN: 978-1-928396-55-0 (print) ISBN: 978-1-928396-56-7 (epub) ISBN: 978-1-928396-57-4 (pdf) DOI: https://doi.org/10.4102/aosis.2018.BK71 How to cite this work: Bwalya, K.J., 2018, The e-Government Development Discourse: Analysing Contemporary and Future Growth Prospects in Developing and Emerging Economies, pp. i–296, AOSIS, Cape Town. Printed and bound in South Africa. Listed in OAPEN (http://www.oapen.org), DOAB (http://www.doabooks.org/) and indexed by Google Scholar. Some rights reserved. This is an open access publication. Except where otherwise noted, this work is distributed under the terms of a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International license (CC BY-NC-SA 4.0), a copy of which is available at https:// creativecommons.org/licenses/by-nc-sa/4.0/.
    [Show full text]
  • The Title of the Article
    OHDSI Cloud Architecture Lee D. Evans, LTS Computing LLC, West Chester PA Abstract The OHDSI cloud provides shared computing and collaboration tool services for the diverse global OHDSI community. It has been developed iteratively over a one year time frame based on expanding community needs. The OHDSI cloud has been operationally very stable and satisfies the performance and operational budget constraints. Declaration of Interests LTS Computing LLC delivers commercial IT projects/services for Life Sciences clients, including pharmaceutical companies. Introduction The OHDSI cloud supports five groups of services: OHDSI Community global collaboration tools Continuous integration build and automated deployment of OHDSI applications OHDSI applications sandbox/demonstration environments running the OHDSI WebAPI OHDSI LAERTES knowledge base ETL operational environment OHDSI research network data repository Infrastructure Ubuntu LTS 14.04 server images running on m3 medium EC2 servers in Amazon AWS. Windows 2012 server image running on an m3 medium server to support Windows based OHDSI tool continuous integration builds. PostgreSQL 9.3 databases running on Amazon EC2 and RDS. OHDSI Community global collaboration tools WordPress Web Site, Dokuwiki Wiki, Discourse Forums. Continuous integration build and automated deployment of OHDSI applications Linux builds are executed using Travis CI software as a service. Windows builds are executed on an AWS hosted Jenkins server. The builds and automated deployments are automatically triggered when new code is pushed to the OHDSI GitHub master repositories. OHDSI applications sandbox/demonstration environments running the OHDSI WebAPI The OHDSI web applications are automatically deployed to Tomcat and Apache servers running within Docker containers. Docker volumes are shared with the Amazon EC2 host servers for persistent storage.
    [Show full text]
  • Apple Report.Pdf
    Bachelor thesis, premaster New Media & Digital Culture, Utrecht University Author: Ryanne Turenhout (3555224) Date: January 28, 2011 Supervisor: Dr. I.O. de Vries Keywords: apple, google, open, closed, platforms, operating systems Android vs. iOS A critical analysis of the open vs. closed debate between Google and Apple Introduction On October 18th, 2010 Steve Jobs, CEO of Apple, made a rare appearance at the 4th quarter 2010 earning call of Apple. He publicly spoke out against Google Android and said, “Google loves to characterize Android as open, and iOS and iPhone as closed. We find this a bit disingenuous and clouding the real difference between our two approaches” (Snell, 2010). He went on to say that the real debate lies in ‘fragmented vs. integrated’. Android is very fragmented, has 100 different versions on 244 different handsets and the user is left to figure out how the Operating System (OS) works. This as opposed to the iPhone where every handset works the same and uses proprietary software with an integrated App Store (Snell, 2010). Briefly, the debate is between Android and iOS, both trying to dominate the mobile market. Android is open source and the iPhone uses the closed source iOS. The two different approaches, open and closed, are at the centre of the debate. The statement of Steve Jobs already implies the importance of this ongoing debate between open and closed mobile platforms. Tim Berners- Lee further shows the importance of this debate in a recent article, ‘Long Live the Web: A Call for Continued Open Standards and Neutrality’. In this article he said the following: [Not] using open standards creates closed worlds.
    [Show full text]
  • Sound, Heuristic Type Annotation Inference for Ruby
    Sound, Heuristic Type Annotation Inference for Ruby Milod Kazerounian Brianna M. Ren Jeffrey S. Foster University of Maryland University of Maryland Tufts University College Park, Maryland, USA College Park, Maryland, USA Medford, MA, USA [email protected] [email protected] [email protected] Abstract Keywords: type inference, dynamic languages, Ruby Many researchers have explored retrofitting static type sys- ACM Reference Format: tems to dynamic languages. This raises the question of how Milod Kazerounian, Brianna M. Ren, and Jeffrey S. Foster. 2020. to add type annotations to code that was previously untyped. Sound, Heuristic Type Annotation Inference for Ruby. In Proceed- One obvious solution is type inference. However, in com- ings of the 16th ACM SIGPLAN International Symposium on Dynamic plex type systems, in particular those with structural types, Languages (DLS ’20), November 17, 2020, Virtual, USA. ACM, New type inference typically produces most general types that York, NY, USA, 14 pages. https://doi.org/10.1145/3426422.3426985 are large, hard to understand, and unnatural for program- mers. To solve this problem, we introduce InferDL, a novel Ruby type inference system that infers sound and useful type 1 Introduction annotations by incorporating heuristics that guess types. Many researchers have explored ways to add static types to For example, we might heuristically guess that a parame- dynamic languages [3, 4, 15, 19, 29, 31, 36, 37], to help pro- ter whose name ends in count is an integer. InferDL works grammers find and prevent type errors. One key challenge by first running standard type inference and then applying in using such retrofitted type systems is finding type anno- heuristics to any positions for which standard type infer- tations for code that was previously untyped.
    [Show full text]
  • Producing Open Source Software How to Run a Successful Free Software Project
    Producing Open Source Software How to Run a Successful Free Software Project Karl Fogel Producing Open Source Software: How to Run a Successful Free Software Project by Karl Fogel Copyright © 2005-2017 Karl Fogel, under the CreativeCommons Attribution-ShareAlike (4.0) license. Version: 2.3088 Home site: http://producingoss.com/ Dedication This book is dedicated to two dear friends without whom it would not have been possible: Karen Under- hill and Jim Blandy. i Table of Contents Preface ............................................................................................................................. vi Why Write This Book? ............................................................................................... vi Who Should Read This Book? .................................................................................... vii Sources ................................................................................................................... vii Acknowledgements ................................................................................................... viii For the first edition (2005) ................................................................................ viii For the second edition (2017) ............................................................................... x Disclaimer .............................................................................................................. xiii 1. Introduction ...................................................................................................................
    [Show full text]
  • Global Discourse and Local Practice: a Study of the Role of Open Source Software in Schoolnet Nambia Magnus Berquist Gothenburg University, [email protected]
    Association for Information Systems AIS Electronic Library (AISeL) Americas Conference on Information Systems AMCIS 2005 Proceedings (AMCIS) 2005 Global Discourse and Local Practice: A Study of the Role of Open Source Software in SchoolNet Nambia Magnus Berquist Gothenburg University, [email protected] Carolina Hafstroem Gothenburg University, [email protected] Jessica Hofbauer Gothenburg University, [email protected] Follow this and additional works at: http://aisel.aisnet.org/amcis2005 Recommended Citation Berquist, Magnus; Hafstroem, Carolina; and Hofbauer, Jessica, "Global Discourse and Local Practice: A Study of the Role of Open Source Software in SchoolNet Nambia" (2005). AMCIS 2005 Proceedings. 45. http://aisel.aisnet.org/amcis2005/45 This material is brought to you by the Americas Conference on Information Systems (AMCIS) at AIS Electronic Library (AISeL). It has been accepted for inclusion in AMCIS 2005 Proceedings by an authorized administrator of AIS Electronic Library (AISeL). For more information, please contact [email protected]. Bergquist et al. Global Discourse and Local Practice Global Discourse and Local Practice: A Study of the Role of Open Source Software in SchoolNet Namibia Magnus Bergquist Carolina Hafström Department of Informatics, Gothenburg Department of Informatics, Gothenburg University, Sweden University, Sweden [email protected] [email protected] Jessica Hofbauer Department of Informatics, Gothenburg University, Sweden [email protected] ABSTRACT
    [Show full text]
  • Ember.Js Front-End Framework – SEO Challenges and Frameworks Comparison
    Ember.js front-end framework – SEO challenges and frameworks comparison Sunil Shrestha Bachelor’s Thesis Degree Program in BITe October 2015 Abstract Author Group Sunil Shrestha BITE10S Title of report Report pages Ember.js front-end framework – SEO challenges and frameworks 43+4 comparison Supervisor Juhani Välimäki IWA Labs Oy, a Finnish company with extensive experience in modern information technology provides professional service in Search Engine Optimization (SEO), online marketing as well as develop mobile and web applications for its clients. In order to provide smooth and better user experience with web applications, the company has adapted front-end dedicated frameworks such as AngularJS, Backbone.js, etc. Therefore, the company is interested in Ember.js– another emerging front-end framework that was first released in 2011. The paper aims to study over current development of Ember.js and compare it with alternative frameworks based on community popularity and their core features. Furthermore, it also addresses some of the most common SEO challenges from Ember.js standpoint. The comparison of frameworks is based on various metrics of each framework such as GitHub stars, commits history, available plugins, Stack Overflow questions, Google trend over time etc. Additionally, core features are also discussed in terms of Model- View-Controller (MVC) pattern. On the other hand, possible solutions for most common SEO challenges in Ember.js are studied and tested via a sample application. Based on the community popularity, AngularJS is clearly proven to be the most popular framework. Nonetheless, based on GitHub commits and other metrics, Ember.js can be taken equally an active and fast growing project.
    [Show full text]