6 ms·

>Syntax / Code folding I was hesitant to add that comment, but it needs to be said. Pushing people into the pit of success is a good thing. Sucks to read 10,00

by nahname 13y ago

>Syntax / Code folding I was hesitant to add that comment, but it needs to be said. Pushing people into the pit of success is a good thing. Sucks to read 10,000 line files? Stop writing 10,000 line files. I also really like how fast sublime is. Coming from an IDE for about 6 years, this is one of the features I like the most. Code folding is bloat. >Whether you think any of these points are valid is your personal opinion I didn't post this under any other assumption. These are all my opinion, as a full time sublime user. >If he didnt want to take user feedback seriously, then why bother with a prominent feature tracking system? I would argue that he is taking user feedback seriously. One of the most difficult things to do with any product is to decide what feedback is valuable and what feedback is not. I think sublime is doing a very good job of this.

Groxx 13y ago
Re folding: what about inherited codebases, via github or your company or whatever? That seems to me to be the vast majority of source code being read / edited in the world, and odds are you can't simply change it on a whim.
- nahname 13y ago
  I think that pain is a great motivator to refactor the code base. I understand that pain, I have been there. But coming from an IDE that supported code folding, I can say two things about it. First, it only helps marginally. Second, it makes occurrences of large files even more prevalent.
Silhouette 13y ago
Pushing people into the pit of success is a good thing. I'm not sure history supports that position, at least in the context of software development. For example, in C++ the syntax for the new-style type cast operators was made deliberately awkward. The argument was that casting is generally not to be encouraged, so doing it should be ugly. What this actually did was encourage almost everyone to ignore the new-style casts and just write the old C-style ones instead, because they worked and didn't make your lines 157 characters long. If you make software development tools, fighting against what software developers want to do is almost never a winning strategy IME. You promote better practices by providing better tools that make those practices easier, not by providing worse tools that make some things harder and hoping that will stop people doing those things instead of ignoring your inferior tools.

by nahname 13y ago

Groxx 13y ago

Re folding: what about inherited codebases, via github or your company or whatever? That seems to me to be the vast majority of source code being read / edited in the world, and odds are you can't simply change it on a whim.

nahname 13y ago
I think that pain is a great motivator to refactor the code base. I understand that pain, I have been there. But coming from an IDE that supported code folding, I can say two things about it. First, it only helps marginally. Second, it makes occurrences of large files even more prevalent.

Silhouette 13y ago

Pushing people into the pit of success is a good thing. I'm not sure history supports that position, at least in the context of software development. For example, in C++ the syntax for the new-style type cast operators was made deliberately awkward. The argument was that casting is generally not to be encouraged, so doing it should be ugly. What this actually did was encourage almost everyone to ignore the new-style casts and just write the old C-style ones instead, because they worked and didn't make your lines 157 characters long. If you make software development tools, fighting against what software developers want to do is almost never a winning strategy IME. You promote better practices by providing better tools that make those practices easier, not by providing worse tools that make some things harder and hoping that will stop people doing those things instead of ignoring your inferior tools.