Sublime Text's Plugin API: It's Python, Sort Of

Re:Sublime Text's Plugin API: It's Python, Sort Of by forrestthewoods on Thursday August 20, 2015 @12:18AM (#10090002)

Wait. Who in the hell releases something on multiple platforms without testing those platforms a single time?! O_o Multiple platform support has always, ALWAYS, required additional work on every project I've ever worked on. Often significant amounts.

[ Parent | on HN ]

Re:Sublime Text's Plugin API: It's Python, Sort Of by ggreer on Thursday August 20, 2015 @05:23AM (#10090748)

When developing a Chrome extension or Firefox add-on or Greasemonkey script, do you test it on Windows, OS X, and Linux?

Sublime Text is the only editor we've had to build platform-specific workarounds for. Atom, Emacs, Neovim, IntelliJ and ilk (PyCharm, WebStorm, etc)... none of them have these sorts of bugs. (They have other bugs, but they're consistent across platforms.) Comments such as, "You didn't test it on every platform?!" are succumbing to hindsight bias.

[ Parent | on HN ]

Re:Sublime Text's Plugin API: It's Python, Sort Of by unfamiliar on Thursday August 20, 2015 @06:25AM (#10090949)

But you said you were hooking into the OS python modules...

[ Parent | on HN ]

Re:Sublime Text's Plugin API: It's Python, Sort Of by ggreer on Thursday August 20, 2015 @10:39AM (#10092100)

Originally, our plugin just used the Python bundled with Sublime Text. Only after discovering these bugs did we add work-arounds that used the system Python.

[ Parent | on HN ]

Re:Sublime Text's Plugin API: It's Python, Sort Of by audiofish on Thursday August 20, 2015 @05:08AM (#10090690)

This is what surprised me too!

That's just asking for problems.

[ Parent | on HN ]