Sublime Forum

Package porting

#1

not sure what happend, but my post got deleted along with replies. i’ll try to repeat it:

after using sublime 2/3 for a few years, mostly with success, it’s time for our company to move on to a long-term solution. there’s just too many bugs not getting fixed.

we picked atom since it’s become rather powerful and fast enough lately, and looks and feels like sublime (a good thing!)

however, our primary concern is a few plugins we need. i wonder if the following packages could be ported to atom (not sure if the authors are reading this forum, but let’s see)

  • cmake build system editor
  • groovy repl
  • pylinter
0 Likes
#2

[quote=“mortont”]not sure what happend, but my post got deleted along with replies. i’ll try to repeat it:

after using sublime 2/3 for a few years, mostly with success, it’s time for our company to move on to a long-term solution. there’s just too many bugs not getting fixed.

we picked atom since it’s become rather powerful and fast enough lately, and looks and feels like sublime (a good thing!)

however, our primary concern is a few plugins we need. i wonder if the following packages could be ported to atom (not sure if the authors are reading this forum, but let’s see)

  • cmake build system editor
  • groovy repl
  • pylinter[/quote]

If you want support for atom, go to their web site.

0 Likes
#3

I guess this is a fair sentiment if one or other of Sublime’s (largely minor) bugs are show-stopping for you or your company. Guess I’m curious as to which though. While I am well aware that Sublime has lots of little bugs, as are most, they don’t get in the way anywhere near enough to warrant ditching Sublime. Like many, while I have some frustration about the recent pace of development with Sublime, in the end a tool is fit for purpose if it does what you need now and for the foreseeable future.

It sounds to me like these plugins add significant value to your company’s workflow. Which, in turn, adds value to Sublime and devalues Atom. Nonetheless, putting aside the obvious ‘go away’ type remarks, let’s try to be helpful…

I’m not familiar with those packages. Assuming they are open source github projects, as many Sublime packages are, the obvious options are:

  1. Port these plugins yourself. This will involve rewriting the plugin logic in coffeescript; mostly this will be fairly straightforward if a little time-consuming. Difficulties will come in the area of differences between Sublime and Atom’s API, requiring some headscratching if Atom’s API’s are different or behave differently.
  2. Pay someone to do (1).
  3. Wait around in the hope that someone else does the hard work for you.

Porting plugins require some confidence in programming and a good familiarity of at least one of the two platforms/languages.

0 Likes
#4

[quote=“qgates”]

I guess this is a fair sentiment if one or other of Sublime’s (largely minor) bugs are show-stopping for you or your company. [/quote]

Showstopping by itself, no, but a lot of people are annoyed enough by some of the bugs (which got worse with yosemite and win 8) that moving to atom makes sense. Most importantly though is the immense extensibility of atom. We are using sublimetext more or less as an ide but we’ve hit the limits of what it can do.

As for your options list, I agree and I’d definitely say we would be willing to pay for porting (unless it takes like months to do)

thanks

0 Likes