3 ms·
Well that's to be expected from a one-man company (IIRC). There used to be a time when you had yearly releases at best for commercial software (and you had to r
by luch 11y ago
Well that's to be expected from a one-man company (IIRC). There used to be a time when you had yearly releases at best for commercial software (and you had to renew your license in order to get the new version). Not every company has to invest in continuous release.
I'm perfectly happy to get infrequent but stable evolutions for Sublime Text.
PS : However if the author could open his source code in order for me to take "inspiration from it" and improving my own Python codebase, that would be great :p
- coldtea 11y ago>Well that's to be expected from a one-man company (IIRC). There used to be a time when you had yearly releases at best for commercial software. The thing is those "dev builds" are not actual releases -- the last 10 or so of them represent at most a few dozen commits, and quite small and isolated features or fixes. So, to put it in other words, the activity is like he has abandoned coding again the last few months (after a short stint of activity that followed a year-long halt).
- jbrooksuk 11y ago> and quite small and isolated features or fixes. This is simply not true. Jon wrote a parser for the new .sublime-syntax files, rather than using .tmTheme files.
- coldtea 11y agoThat was released in "Build 3084 / Release Date: 8 April 2015". I'd also count the "new regex engine" as a major feature, landing in 3085, 5 May. Since then, for 7 builds, it has been small scale fixes and minor improvements, even them stopping altogether around July 10. http://www.sublimetext.com/3dev http://www.sublimetext.com/3dev I also remember what the development pace was like for ST2 -- those builds were coming up several times a week even, so that's something to compare against.