![]() ![]() I’m optimistic this time this time we’ll see real change. Been wanting to know exactly what changed inside buffer modification events? ST4 is the release we’re likely to get it. Yeah, there’s a few bugs that annoy me, but no data losses or anything serious. ![]() So I’m personally excited, having followed ST development since 0.x, because this will be the release that has everything that’s been postponed in ST2 and ST3, and all (or a lot) that’s been up Jon’s sleeve for under the hood changes. Having said that, ST3 still feels much the same in spirit to the windows only, xml configured, editor I fell in loves with years ago. ST3 starts in an instant and json config is better than the days. People have complained about the disruption / evolution ratio in past releases, but it really hasn’t been that bad. I’m glad Jon still has the energy, desire and focus to push the envelope, and leave the past behind. If you haven’t checked out the bugtracker ( /teams/st-undocs/fundraiser) the original series is a goldmine of Sublime Text secrets.Īs always, feel free to email me with specific questions about Sublime Text’s future: wrote:īack in the day, before package control, and the countless plugins, and large community, there were just a small group of people excited about a nice new editor, and the possibilities. Sublime Text continues to flourish through this slower period thanks to some amazing users. I’m the only other employee at the moment, and my job relates to sales and day to day operations. textwrangler vs sublime code After 6 years of work and lots of anticipation, the source code to the 2.0 version was released to the public. Many of you have kindly offered your assistance in the development of Sublime Jon has made the decision that he will complete version 3.0 himself, and from there we will begin expanding the team of developers. However, development is still active: when I spoke to Jon today he advised me that not only does he expect an update to the beta in August, he has also started mapping out some frameworks for version 4 which will help guide future development. Being a bit of a perfectionist probably contributes to the dearth of feature adds. We dropped back down to one developer earlier this year, and because that developer is also the director of the company, speed of updates was sacrificed in exchange for business planning, applying for a new payment platform and a vacation. We haven’t sold out to atom.io, Jon hasn’t died, there has been no hostile takeover by TextWrangler. ![]() However, wbond rightly pointed out that not everyone is digging deep in the forum archives for status updates, so I’m sticking this front and centre: I’ve had a flood of emails in the past few months regarding the lack of updates from Sublime Text, and responded to this previously ( viewtopic.php?f=2&t=15477&hilit=kari&start=50#p58951). ![]()
0 Comments
Leave a Reply. |