On Tue, Aug 6, 2013 at 5:27 AM, Robert Marcano <robert(a)marcanoonline.com> wrote:
> You make the decision by installing a js-foo package, just like
> make the decision to provide a web application by installing a package
> for it.
"You make a decision by installing a package" is a really problematic
model, e.g. because packages can be dragged in by dependencies.
being encouraged as a language for desktop applications? So all those
libraries that can be used on desktop and web clients will be shared by
default if I install a desktop application that need that library and a web
application that never uses that library? This is madness, why not share
/usr/bin via NFS too by default
There is actually a precedent for that - our default httpd
configuration aliases /icons, see e.g.
. OK, these are "only"
public domain; then let's see httpd-manual, which publishes
Apache-licensed documentation in /manual.
(That's not necessarily a good argument that it's OK to do this way, I
just wanted to point out that this is not that new.)