13 ms·
Looking at the sample chapter, this book seems reasonably well written and might be a good buy for someone new to ST who wants to get up to speed quickly. I th
by Silhouette 12y ago
Looking at the sample chapter, this book seems reasonably well written and might be a good buy for someone new to ST who wants to get up to speed quickly.
I think calling it a book for power users is highly optimistic. Much of it seems to be more like the manual ST should have had but never has, describing routine tools and pointing out keyboard shortcuts that you could find for yourself just exploring the default keyboard map. That is certainly a useful gap to fill, but there seems to be little if anything in the table of contents about real power user features like defining or customising languages, templates/snippets, themes, plugins, etc. I hope the choice of title doesn't lead to disappointment from actual power users while causing those who would enjoy and benefit from the book to go elsewhere.
I did notice that the sample chapter PDF has quite a few obvious layout problems, and that the expanded TOC on the web site has obvious typos, so the jury is out on editorial/production quality.
As a final comment, the author seems very keen on ST3, which makes me hesitant. I gave up and installed ST3 myself a little while ago, after too many packages I relied on self-updated into just not working any more on ST2. Now instead of a productive text editor that I enjoyed and recommended a year or two ago, I have a crash-prone, bug-ridden mess, which just has different packages I used to rely on that don't work reliably instead. So I'm pretty down on the whole fragmented ST ecosystem and lack of progress/support for existing customers right now. While I assume none of this is the author's fault, perhaps the timing of this book launch is unfortunate; it might be a better buy if and when ST3 and its package ecosystem are up to production quality, updated to reflect whatever the best available supporting packages are at that time.
- wldcordeiro 12y agoI've been using ST3's dev builds with no issues whatsoever so I don't see how it's a crash-prone, bug-ridden mess. Maybe your crashes are a result of plugins you use?
- Silhouette 12y agoIt seems to crash occasionally (or at least hangs for long enough that it might as well have) even with no plugins at all installed, with build 3065. Certain plugins, particularly more heavyweight ones like SublimeCodeIntel, crash so often for me that they are completely unusable with ST3. But the bottom line is it doesn't really matter whose fault it is. I used to have an editing suite using ST2 and powerful plugins like SublimeLinter and SublimeCodeIntel that worked very well for me. Now I don't, and no combination of ST version and available plugins for that version will get me back there short of figuring out which packages I used to have and then going back to ST2 and manually installing historical versions of each of them assuming they are still available. Since ST without those powerful plugins is a decent text editor but nowhere near adequate for professional software/web development, the currently fragmented and broken ST ecosystem is their problem one way or another even if it isn't supposed to be their fault.
- Walkman 12y agoNo, ST3 is still not very stable. It crashes for me every day, have to restart multiple times.
- xs 12y agoMaybe when you get into defining custom languages you're going past "power user" and into the "developer" realm? I think by understanding and using the topics covered in the book you can certainly call yourself a power user by the end.
- sandipc 12y ago> Does this book cover Sublime Text 2 or 3? > While you should be migrated to version 3 already, this book covers both versions 2 and 3 - when there are differences or new functionality in a later version I make a point of saying so and offer solutions to users still on version 2. Yeah, I guess I just don't understand why I "should be migrated to version 3 already" when a non-dev build has yet to be released. Seems like a nice book otherwise.