News for hackers. Stuff that matters.

A comment on Why I wrote 33 VSCode extensions and how I manage them. Parent comment

Re:Why I wrote 33 VSCode extensions and how I manage them by coldtea on Tuesday November 06, 2018 @02:56AM (#18389168)
>I've had entirely the opposite experience. Have you ever tried to install a package in Sublime? You have to use a separate tool, Package Control, whose installation instructions are arcane:

Not since the last 5 years or so, where it's built-in to ST.

[ Parent | on HN ]
Re:Why I wrote 33 VSCode extensions and how I manage them by Already__Taken on Tuesday November 06, 2018 @08:44AM (#18390878)
This has only officially been built-in since last year with ST3 which took an age to come out of beta.
[ Parent | on HN ]
Re:Why I wrote 33 VSCode extensions and how I manage them by coldtea on Wednesday November 07, 2018 @03:40AM (#18397844)
I've been using ST3 for like 5 years (in beta) and it was just as stable as the "stable" release.

There was absolutely no reason to use ST3 for the past 3 years if you already used ST/ST2.

That was already the case for ST2, which was stable for years before it officially announced it was "stable".

Stable/unstable for STx are just labels, they don't actually reflect the state of stability. Plus all the real work (new plugins, etc) happened on the "beta" ST3 side for years...

[ Parent | on HN ]