Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Not another vendor-lock-in package manager. And, very predictably, no end-to-end integrity and nonrepudiation. smh.


sort by: page size:

More non-standard, closed source, vendor lock in.

vendor agnostic doesn't exist

Microsoft would never do vendor lock-in (:

Vendor lock-in isn't good for users either.

I try to avoid all products with vendor lock-in specifically because it is so predictable.

Nah.. Just another closed source browser for `vendor lock-in`. no thanks.

edit:word


Vendoring is a last resort, that sounds like going back to the stone ages of package management. Why would I want that?

I don't see vendor lock-in as a net win for anyone but the vendor.

I guess you haven't ever heard of vendor lock-in.

You do lock yourself into the software, but at least not a vendor.

This doesn't seem to have any relevance to "vendor lock-in" though.

Normally I don't give a crap about vendor lock-in, but this would be an exception where I'd agree with you.

Though most people are just going to use a framework plugin to manage the messaging layer, so what's behind that is largely irrelevant.


"Vendor" lock-in is everywhere, for the most part. Yeah, if I didn't like something Linux, Apache, GNOME, etc were doing, I could fork the source and go my own way, but is that realistic for even 99% of the people out there?

No. I'll still have to venture off and find an alternative or just deal with it.


Why is vendor lock-in a concern if no other vendor offers that functionality?

Avoiding vendor lock-in is the only quasi-sane reason I can think of.

If anything, vendor lock-in is consistently underblown.

I’m surprised it didn’t mention vendor lock-in, which is definitely a selling point for open source.

Locked in maybe, but not vendor locked in if the language is open source.

It would be unwise to submit to vendor lock-in.
next

Legal | privacy