Hi Francisco. Thank you for your answer. I understand that it's hard, if
not impossible, to provide the same experience locally. Especially instant
access to the entire npm is understandably resource-heavy.
There are, however, two things which make a local version very important:
First and most importantly, sensitive code which can't be uploaded to
servers not in a company's control. That's for example the case for some of
my projects. A closed source, paid version is also very fine for this use
case. I already pay for tools like linqpad to quickly test .NET code. This
would presumably allow me to use a private npm repo as well.
Second thing is, I have to have some kind of assurance before I invest in a
tool. I sincerely hope that your great work keeps getting updated and used
at least for as long as node itself lives. However, companies change
direction all the time and at least a pledge to open source if it comes to
that would go a long way to satisfy many people who'd invest in your tool.
I'm willing to wait a few seconds for npm to download a module anytime I
require something new, if it means that I can keep using this great tool
for the foreseeable future.
17 Eyl 2016 03:05 tarihinde "Francisco" firstname.lastname@example.org yazdı: