IMHO there's no need for an OS version of sublime. Sublime is working fine, stable, has a free unlimited trial. It makes no sense to make a verbatim "copy". Maybe he can prepare a release into OS if the proverbial bus hits him?
Lime Text: Open Source Sublime Text clone
111–120 of 251 posts
Re: Lime Text: Open Source Sublime Text clone
#112Few months ago I moved from ST but I would come back to a similar open source solution if it implemented IDE features on packages. So I can have two shortcuts, one opens with everything IDE-like, the second one would only load a few packages and be very Sublime-ish. Fast and simple.
Out of interest what did you move to?
PhpStorm (jetbrains.com/phpstorm), but it's not open source :(
there are lot of free options too, like NetBeans
Re: Lime Text: Open Source Sublime Text clone
#113Earlier quoted context omitted.
Both Emacs and Vim are updated regularly: http://en.wikipedia.org/wiki/GNU_Emacs#Release_history http://en.wikipedia.org/wiki/Vim_%28text_editor%29#Release_h... In between major releases they have tons and tons of bug fixes (Vim probably has hundreds per release). Editors can suffer a lot from code rot since they have to integrate with a lot of things. An Open Source version could be quite interesting from Sublime's…
Looking at the links you posted - vim is updated once every 3-4 years, emacs - once a year. Looking at sublime text release log ( http://www.sublimetext.com/blog/ ) it's been updated much more often than emacs and vim combined.
It's the difference between updated and released. The last Emacs commit was this morning around 9:30am. There is ongoing development on both editors.
Re: Lime Text: Open Source Sublime Text clone
#114If there is one app I've always been thrilled to pay for, it's Sublime Text. I've purchased and renewed the licence ever since v1 came out. While it may not be open sourced, you can see it was created with a lot of love for code and openness. Today there are thousands of amazing plugins to enhance it. And though I fully respect the open source initiative, I, for once, am very happy to support / give some money to a p…
60 bucks for an editor is quite expensive I think. There are nice alternative to such an editor. I wonder what features makes sublime text so much valuable...
>> 60 bucks for an editor is quite expensive I think.
I remember in the 90's, the big editors Visual SlickEdit and BBEdit were like $200 each!
Re: Lime Text: Open Source Sublime Text clone
#115Isn't Atom the open source Sublime Text clone?
"The"? This isn't the Highlander, there can be more than one.
Re: Lime Text: Open Source Sublime Text clone
#116I wish they wouldn't attach themselves to the sublime brand. It's not theirs, and it's pretty shady to ride another project's coattails when their intent is essentially to cannibalize it by being sublime-but-free. You can discuss the merits of open source and paying for tools all you want, but basically their goal is to put a man out of business who's made something that a lot of people love, because he has the gall…
I agree, but the main reason for most people (I can't comment on the author's intention) is that Sublime is lacking updates and transparency about the development.
They did announced something recently, like getting ready for ST 4. And 3 is not even a major upgrade from ST2, IMHO.
Re: Lime Text: Open Source Sublime Text clone
#117Earlier quoted context omitted.
I can give you my source code and allow you to change it, but if you want to execute a compiled result of that source code I can still ask you to pay me for it. And while there is no physical thing stopping you from executing the binary without my permission, I think you would still be unlikely to do so, if you know how much work I've put into it and you know that I would like you to give me a few bucks. I'd trust yo…
You can do that, but it wouldn't be considered "open source" by most people, or by the OSI. http://opensource.org/osd-annotated > The program must include source code, and must allow distribution in source code as well as compiled form. ... > The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software. ... > The license mus…
Your quotes say "distribution", not "except execution"
Re: Lime Text: Open Source Sublime Text clone
#118I wish they wouldn't attach themselves to the sublime brand. It's not theirs, and it's pretty shady to ride another project's coattails when their intent is essentially to cannibalize it by being sublime-but-free. You can discuss the merits of open source and paying for tools all you want, but basically their goal is to put a man out of business who's made something that a lot of people love, because he has the gall…
I don't think people care so much about how it's 60$. At work that makes little difference to me. The big thing is how this is open source.
Re: Lime Text: Open Source Sublime Text clone
#119Earlier quoted context omitted.
Both Emacs and Vim are updated regularly: http://en.wikipedia.org/wiki/GNU_Emacs#Release_history http://en.wikipedia.org/wiki/Vim_%28text_editor%29#Release_h... In between major releases they have tons and tons of bug fixes (Vim probably has hundreds per release). Editors can suffer a lot from code rot since they have to integrate with a lot of things. An Open Source version could be quite interesting from Sublime's…
Looking at the links you posted - vim is updated once every 3-4 years, emacs - once a year. Looking at sublime text release log ( http://www.sublimetext.com/blog/ ) it's been updated much more often than emacs and vim combined.
> Looking at the links you posted - vim is updated once every 3-4 years, emacs - once a year. Looking at sublime text release log (http://www.sublimetext.com/blog/) it's been updated much more often than emacs and vim combined.
Honestly though. Emacs was first released almost half a century ago. Its core is fairly feature-complete. It doesn't need intense development and constant releases.
Besides, at least for Emacs, one of the main driving principles is for it to have a good & stable core, and have all the bells and whistles delivered via extensions and packages. And those extensions gets updated continuously. Often from git commit to git commit, depending on author.
When you have decades worth of customizations and ecosystem-code to consider, keeping the core stable is the only strategy you can possibly choose.
Your comparison isn't apples to oranges, it's 40 years old whisky to diet coke.
Edit: Half a century, not decade. Thanks dragonwriter.
Re: Lime Text: Open Source Sublime Text clone
#120Earlier quoted context omitted.
Looking at the links you posted - vim is updated once every 3-4 years, emacs - once a year. Looking at sublime text release log ( http://www.sublimetext.com/blog/ ) it's been updated much more often than emacs and vim combined.
> Looking at the links you posted - vim is updated once every 3-4 years, emacs - once a year. Looking at sublime text release log ( http://www.sublimetext.com/blog/ ) it's been updated much more often than emacs and vim combined. Honestly though. Emacs was first released almost half a century ago. Its core is fairly feature-complete. It doesn't need intense development and constant releases. Besides, at least for Ema…
> Emacs was first release almost half a decade ago.
Closer to half a century, which I guess reinforces your point.