Bower.js and the Future of Client-side Modularity
$ bower install jquery bower cloning git://github.com/components/jquery.git bower cached git://github.com/components/jquery.git bower fetching jquery bower checking out jquery#1.8.1 bower copying
The output style is like most node.js CLIs in that it is very terse. While I personally prefer longer messages the output shows all information relevant to the task at hand.
The above example clearly illustrates the simplicity of Bower. However, this simplicity comes at a price, a lack of configuration options. The ability to configure names of folders and files is absolutely crucial for both development and deployment. Therefore, integrating bower into an existing project seems both tedious and error-prone. Similar trade-offs are made consistently across the entire application, for example Bower only supports a flat dependency tree.
Technologist at Sobel Software Research
William Rudenmalm is a european technologist passionate about the next big thing and the people building it. William is particularly interested in scaling engineering organizations and navigating trade offs of architecture and velocity. In the field of computer science, his expertise lies in distributed systems, scalability and machine learning. Among the technologies William is particularly excited about are Kubernetes, Rust, nats, Kafka and neo4j.