未加星标

Modular Code Libraries FTW

字体大小 | |
[前端(javascript) 所属分类 前端(javascript) | 发布者 店小二03 | 时间 2017 | 作者 红领巾 ] 0人收藏点击收藏

Thanks to the fact that I work alongside a bunch of awesome people, today I’ve been introduced to the date-fns library, and it struck a chord with me because it the epitomises a way of thinking about creating manageable, maintainable sourcecode.

Code is ultimately a solution to a problem. As developers we’re constantly writing code, and the more code we write, the more experience we acquire, the better we get. A big advantage to having previously written code is in being able to reuse that same solution in the future. The advantage to using other people’s code, when it comes in the form of a library or a framework, is in being able to use their solutions without having to invest your own time in the fine details of a solution.

Modules?

Modular code (for the purposes of this piece at least) are those reusable snippets of code which we copy & paste between projects, or those small, tightly-focussed libraries of code with a well-defined scope and purpose. Moment.js and Vibrant.js are two examples of libraries which I’ve used recently, in addition to date-fns . The key thing about these libraries is that they’re simple enough to drop into an existing project and quickly get it working without having to restructure large swathes of the existing code.

Modules vs. Frameworks

Frameworks are a larger beast to introduce to ― or remove from ― a project. For everything they offer, it’s not really flexibility and universal suitability that’s high on the priorities of a framework.

Adopting React, Angular, Backbone or any of the other javascript frameworks out there ends up locking your source code into its own patterns. Once you’ve adopted a framework you’re more-or-less stuck with it, with the structure, with its quirks, with its ways of thinking, and you can’t escape it without a considerable effort and an evitable rewrite. Modules on the other hand, those you can effectively find drop-in replacements for.

Easier to manage, easier to maintain.

Being able to easily replace portions of your source code is great for shifting requirements, and seems like a great idea for developing code in line with the Agile methodology. It’s entirely possible to develop without using a framework, and if you do so you don’t lose that flexibility. Modules also have a much shorter learning curve than an entire framework, so it’s much easier to get to grips with them and use them properly, the learning curve is shallower for the codebase as a whole and thus the long-term maintenance of a project is easier to handle.

In short I prefer a modular, libraries-based codebase than a particular popular-right-now framework. And date-fns is one of the better implementations of a format-agnostic library of code that I’ve seen.

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

主题: ReactJava
分页:12
转载请注明
本文标题:Modular Code Libraries FTW
本站链接:http://www.codesec.net/view/523159.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(75)