I'm not sure what it is, but something feels very wrong to me about sublime package control. It might be the instructions for submitting new packages. It might be the difficulty of installing a bunch of packages at once.
It strikes me as harsh to describe those things as "very wrong". Maybe it's just me, but for me, things that are "very wrong" are things like inequality, unconstitutional NSA spying, and watermelons with seeds. You know? Truly important stuff.
edit: Is my tongue-in-cheek opinion really that bad? Am I, too, "very wrong"?
For me it's the install method. I don't like the 'copy this code into your console' approach; all it takes is a subtly-hacked server and someone can redirect that URL request or cause other mischief.
I just don't understand why Package Control isn't part of the standard Sublime Text 3 package by now. Do any Sublime users not use Package Control?
This is my feeling as well. The console shenanigans feel odd to me simply because it feels like it should already be there. There is a coolness to it, though, since it clearly demonstrates how effectively the interface can be modded from just a "simple" command.
No doubt there are perfectly reasonable business explanations for why Sublime doesn't ship with it, but I wouldn't consider upgrading from 2 until 3 was supported.
Anecdote on why the console code is bad and good: by coincidence this afternoon I decided to try ST3, and before using it spent about an hour trying to get Package Control working via the git repo route [1] (Sublime was already inside a local repo, so I had to RTFM git submodule stuff to appease the git_binary error); that went... poorly. I [ab]use Git's functionality, but don't grok it's inner workings well enough to feel like I can use submodules without contaminating the super repo, and eventually gave up when I accidentally came across the page that has the new command [2]. Bam it's working without trouble (after modifying it for the corporate proxy). Like magic it just worked, which was awesome, but silly that something so useful would have any barrier to entry at all.
TL;DR: Package Control is an essential element of the joy of Sublime Text, so it's a little mystifying why it's not just built in.
The idea of bundling Package Control with Sublime Text has been proposed many times, and more than once directly to Jon. If I recall correctly, I don't think he replied directly to the suggestion.
My guess is that he would prefer to keep them separate for support purposes. If they are bundled then users may have the expectation that Sublime HQ Pty Ltd will support it.
Have you seen the current installation page (https://sublime.wbond.net/installation)? I thought I made it pretty clear with the large orange banner the potential risks of the "Simple" method.
Honestly, by this point my brain is trained to ignore anything on a web page I'm not interested in. Ads, warning messages, those annoying EU cookie warnings...
Don't get me wrong, I don't think there are bad intentions here or that you're not doing due diligence to warn users, I just think this type of installation method should be discouraged in general.
