Comment 333 for bug 1575053

Revision history for this message
Patrick K. Etienne (sulaweyo) wrote :

It's been at least a few years since I've last checked on this issue. When initially exploring snap as a solution for application packaging, I discovered that the snap developers had decided to address a technical / security related issue by implementing a "hard coded" solution - one which, though maybe convenient for snap developers, goes against popular (an understatement) both formal and informal standards (mentioned in many previous comments). With this being the case, and since that original date a few years back, I have not developed apps in or utilized existing apps using snap and have instead used other solutions. Id est, my development and utilization behavior is as though snap does not exist. Snap will continue not to exist as an option (for my uses) until (at least) this issue has been adequately resolved.

As a side note, others have mentioned the "arrogance" involved in this decision. I've encountered plenty of what I would characterize as "questionable" decisions by development teams, however I have to say that this one is certainly "outstanding", not at all in a good way. I don't have the time or inclination to probe further into why hard coding a directory location is a feasible solution to a security issue, but fortunately snap has enough competition that I can effectively forget that snap exists for years at a time without either feeling like I'm missing anything or having the lack of it impact my productivity.

Not that alternatives to snap are by any means perfect, but thank goodness for the competition.

Cheers all =)