I think the title of this should be updated, as it is not correct. The sublime text homepage has been displaying builds for sublime text 3 since mid February[0] Sublime Text 3 is still in beta. [0] https://web.archive.org/web/20160211015747/http://www.sublim...
Sublime Text 3 marked as recommended build
101–110 of 135 posts
Re: Sublime Text 3 marked as recommended build
#102Honestly I never used it because of its philosophy: - it's not open source (which is something bad nowadays for a text editor) - it's not really customizable (I must use my text editor all the day every day, I need an environment crafted on my needs) - it's not free (why should I pay for something that is available for free with Atom?) - it has python scripts... really? python? why?
I'm glad it's not, because if it were open source, it'd look and feel like Windows 98 software (Notepad++). Open source serves developers, not users.
>it's not really customizable
How strange, cause my build is.
>it's not free
In the Winrar sense, yeah. You get an unintrusive popup in the background after a few saves.
>it has python scripts... really? python? why?
This one's kind of like an appeal to the current year in social issues. There's no substance to even respond to.
Re: Sublime Text 3 marked as recommended build
#103I've never used any of those new editors (ST, Atom, VS Code, ...). Can anyone compare them to the more classic ultraedit? Or said differently: Why would I chose ST3 over one of the classic editors?
Atom and VS Code use the same basic underlying technology and are JavaScript under the hood. With both you can actually open up a chrome like web inspector to help you write and debug plugins. These editors are Open Source and funded by companies whose main source of income is not the editor, but have money (GitHub and Microsoft). Sublime Text is an editor that brought a lot of new ideas that many editors now adopt (…
Re: Sublime Text 3 marked as recommended build
#104Now if only I could afford it :D
I understand you're joking, but this is important. It's $70. I know that's a lot to some people, but if you're selling your time as a developer it's probably quite a lot less than 1/2 a day at your usual rate. For a tool that will save you many days a year (and increase your bottomline as much), that's really cheap. If you were a designer and needed Adobe's tools you'd be paying much every month. If you're using Subl…
Re: Sublime Text 3 marked as recommended build
#105I think the title of this should be updated, as it is not correct. The sublime text homepage has been displaying builds for sublime text 3 since mid February[0] Sublime Text 3 is still in beta. [0] https://web.archive.org/web/20160211015747/http://www.sublim...
Ok, we'll use your phrase as the title. If someone suggests a better (more accurate and neutral) title, we can change it again. (Though that may have to wait overnight...)
Re: Sublime Text 3 marked as recommended build
#106Honestly I never used it because of its philosophy: - it's not open source (which is something bad nowadays for a text editor) - it's not really customizable (I must use my text editor all the day every day, I need an environment crafted on my needs) - it's not free (why should I pay for something that is available for free with Atom?) - it has python scripts... really? python? why?
>it's not open source I'm glad it's not, because if it were open source, it'd look and feel like Windows 98 software (Notepad++). Open source serves developers, not users. >it's not really customizable How strange, cause my build is. >it's not free In the Winrar sense, yeah. You get an unintrusive popup in the background after a few saves. >it has python scripts... really? python? why? This one's kind of like an appe…
2. I don't mean "change the syntax color", I mean, change every single pixel of its UI.
3. it's not free, it means that IT'S NOT FREE, you can just evaluate it, and then you MUST buy it. If you are using it for anything more than evaluating, you are violating its license.
4. seems fair, I don't really like python, and I think that JS based editors are much easier to hack and to develop plugins for.
Re: Sublime Text 3 marked as recommended build
#107Why are modern text editors so slow? Here's an editor that I use from 1996 opening up a 1GB file of randomly generated bytes (dd if=/dev/urandom of=random_bytes.txt bs=64M count=16): http://i.imgur.com/BVln6Y2.gif -- it opens instantly and I can scrub to any point in the file with no delay. I've yet to find a modern editor that beats my 1996 one.
Modern editors are much more that file browsers. They do static analysis, syntax colouring, linting and many more things (depending on what plugins you have installed). I still like to open a plain vim and just focus on the task at hand without the magic, but that's just not how most web developers work these days.
More importantly, a lot of this functionality is down to simply not thinking about consequences. E.g. try starting a typical Emacs installation on a box that has a network but where the DNS setup is broken, and enjoy waiting for DNS lookups to time out before it starts... (I'm sure there's an easy fix; I'll admit to being lazy and not having looked for how to prevent it and rather "just" fix my DNS when it's happened)
All to often "nice to have" functionality ends up in the critical path of startup rather than lazily initialize in the background.
Re: Sublime Text 3 marked as recommended build
#108Earlier quoted context omitted.
I disagree. I had tried out Atom for a little bit (after the v1 general release) and more than once I lost my entire workspace. Either through a computer crash, Atom crash, or something else. Maybe I didn't configure something right, maybe I didn't. Quite frankly I don't care, I think that always properly persisting all unsaved work should be a default. Sublime always persisted all of my workspaces and open tabs perf…
I concur: Sublime Text's persistent workspace is really great.
Re: Sublime Text 3 marked as recommended build
#109Earlier quoted context omitted.
Ok, we'll use your phrase as the title. If someone suggests a better (more accurate and neutral) title, we can change it again. (Though that may have to wait overnight...)
The current title ("Sublime Text 3 is still in beta") sounds like an attack to me, implying slow development. I'd suggest "Sublime Text 3 marked as recommended build (Feb 2016)", or something like that. More wordy, but more accurate.
Re: Sublime Text 3 marked as recommended build
#110Earlier quoted context omitted.
> For my needs, VSCode is already better with better plugins I bet the Sublime spell-check plugin doesn't send your entire file to a third-party server over plain http.
Does VScode's?