3 ms·
> you don't have to research how to achieve the equivalent in another ecosystem is somewhat contradicted by > browserify the thing and you're done Browserify
by falcolas 12y ago
> you don't have to research how to achieve the equivalent in another ecosystem
is somewhat contradicted by
> browserify the thing and you're done
Browserifying a library might seem conceptually simple, but if it was written with a particular usage in mind, it will really include writing a set of non-trivial shims to make it work with, say, Ajax instead of `fs`.
If, on the other hand, you actually understand the problem at hand and are willing to write code instead of plumbing libraries together, you can frequently express the solution to that problem in remarkably few concise lines of code in any language. This alleviates the need for others to learn both the problem domain and the quirks of the library chosen to address that problem.