This reminds me of the layers concept from https://www.destroyallsoftware.com/talks/a-whole-new-world
Sublime Text 2 plugin to show git commit history for selected line(s) of code
31–40 of 45 posts
Re: Sublime Text 2 plugin to show git commit history for selected line(s) of code
#32Earlier quoted context omitted.
Its easier to start from a lightweight text editor and add only what you need as opposed to start with an IDE and trim the fat, and pray it won't break.
Actually, the first time you start IntelliJ, it will walk you through all the plugins per category. If you don't select anything, you will mostly have the same effect. Of course, the result won't be as light as Sublime text, because it is already a Java IDE :). Also, I don't really see the point. I start or restart my IDE (IntelliJ) one time a week. So, it's not really the startup time that matters. Once started, Int…
> I start or restart my IDE (IntelliJ) one time a week. So, it's not really the startup time that matters.
So I assume you don't use your IDE for modifying local configuration files, or taking random notes, then. Startup time (and having multiple lightweight instances) is important in these cases.
People replace Notepad/vi with Sublime Text, in order to get all the benefits and power they're used to in Sublime Text when editing even the most mundane or ephemeral document. You can't really do that with IntelliJ.
Re: Sublime Text 2 plugin to show git commit history for selected line(s) of code
#33There is a plugin (found within the package manager) called simply 'Git' that does this -- you just call Git Blame from the bar (CTRL SHIFT P) and it'll show you a line-by-line history of the whole file or selection.
Re: Sublime Text 2 plugin to show git commit history for selected line(s) of code
#34Disclaimer: I love ST and use it everyday and this is not against this plugin in particular, just the idea of extending your editor to be an IDE. When people extend their text editor (be it sublime, vim, emacs) with all these (often outdated) plugins i am left wondering why there is still so much hate for IDEs ? I use IDEs from Jetbrains for most of my stuff and they do all these things oob with a consistent UI and a…
I personally run Sublime Text and an IDE at the same time (for static languages). I use Sublime Text for the majority of text editing and whip out the IDE when I want to explore an API. The IDE is also good for debugging and heck, it gives you a build system for free.
Re: Sublime Text 2 plugin to show git commit history for selected line(s) of code
#35Does this work w/ Sublime Text 3 too?
Re: Sublime Text 2 plugin to show git commit history for selected line(s) of code
#36Disclaimer: I love ST and use it everyday and this is not against this plugin in particular, just the idea of extending your editor to be an IDE. When people extend their text editor (be it sublime, vim, emacs) with all these (often outdated) plugins i am left wondering why there is still so much hate for IDEs ? I use IDEs from Jetbrains for most of my stuff and they do all these things oob with a consistent UI and a…
My problem with the IDEs I've used is they aren't very good at editing text (especially Eclipse).
Re: Sublime Text 2 plugin to show git commit history for selected line(s) of code
#37Disclaimer: I love ST and use it everyday and this is not against this plugin in particular, just the idea of extending your editor to be an IDE. When people extend their text editor (be it sublime, vim, emacs) with all these (often outdated) plugins i am left wondering why there is still so much hate for IDEs ? I use IDEs from Jetbrains for most of my stuff and they do all these things oob with a consistent UI and a…
One of the reasons I dislike IDEs is the same as the reason I dislike things like janus or oh-my-zsh, and the same reason that I removed my employer's 'source ...' from my vimrc at work. Poorly considered collections of nonsense that I don't want to be thrust into.
Furthermore, I select my plugins carefully with future-proofing as my number one priority. This means that I do not use (or at least certainly do not rely on) software that I am not confident will stick around at least until I retire or software that I could not reproduce if necessary. I am confident that Vim will stick around that long and I am confident that the plugins which I use with Vim will either continue to work, become obsolete when Vim absorbs their ideas, or are tools that I could recreate myself should future vim updates ever break them (this has not been happening so far).
In some cases, these constraints prove problematic. One example is web browsers. I have zero confidence that Firefox or Chrome will exist and/or be recognizable in even 10 years. I therefore do not rely on any special Firefox or Chrome functionality, particularly any plugins or extensions. Additionally I split my usage of the browsers evenly between the two in an attempt to ensure that I do not become reliant on Firefox or Chrome specific behavior or abilities that I may lose access to in the future.
My problem with Firefox/Chrome is a problem that I have with IDEs. They come and go, they change and "improve" over time in ways that are not backwards compatible from a UX perspective. I want none of that. A carpenter does not worry about the interface to his tablesaw changing in 10 years, forcing him learn a new set of skills to experience the same functionality. That sort of stability is what I strive for.
Edit: As for text editor plugins typically being out of date... I just checked. The most 'out of date' plugin that I have is actually just my colorscheme, having it's last commit on Fri Mar 2 14:59:51 2012 -0600. All of the rest have had commits in the past 6 months. A quarter of them have had updates in the past month.
Re: Sublime Text 2 plugin to show git commit history for selected line(s) of code
#38Disclaimer: I love ST and use it everyday and this is not against this plugin in particular, just the idea of extending your editor to be an IDE. When people extend their text editor (be it sublime, vim, emacs) with all these (often outdated) plugins i am left wondering why there is still so much hate for IDEs ? I use IDEs from Jetbrains for most of my stuff and they do all these things oob with a consistent UI and a…
One of the reasons I dislike IDEs is the same as the reason I dislike things like janus or oh-my-zsh, and the same reason that I removed my employer's 'source ...' from my vimrc at work. Poorly considered collections of nonsense that I don't want to be thrust into. Furthermore, I select my plugins carefully with future-proofing as my number one priority. This means that I do not use (or at least certainly do not rely…
I find that take quite interesting considering the rapid pace at which software and computing changes over time. I would expect that by the time I retire in 30 years that nothing that I do right now will exist or be at all relevant.
I use certain software right now for programming that is completely different than what I used even two years ago. I work in completely different technology stacks and completely different tools.
Why would restrict myself to only using a set of tools that I KNOW will existing 20-30 years? What happens when some breakthrough technology comes that comes with it's own stack and toolset? Do you ignore it or adapt?
I actually enjoy switching between various technologies and tools. You get a different perspective, learn new things, get out of the rut and into a new challenge.
I really hope that in 3 years I'm not using the same tools I am using today.
Re: Sublime Text 2 plugin to show git commit history for selected line(s) of code
#39Disclaimer: I love ST and use it everyday and this is not against this plugin in particular, just the idea of extending your editor to be an IDE. When people extend their text editor (be it sublime, vim, emacs) with all these (often outdated) plugins i am left wondering why there is still so much hate for IDEs ? I use IDEs from Jetbrains for most of my stuff and they do all these things oob with a consistent UI and a…
I can't speak for others, but for me, the main thing that has kept me away from IDEs is lag. Every IDE I've ever used (IDEA, Eclipse, NetBeans, Visual Studio) has always interrupted my workflow on a regular basis in order to recompile something or update some index or other. In statically typed languages, that's often a tradeoff I'm happy to make; IDEs give you a lot more information than text editors in that case. B…
It seems the main question here is cost/benefit. For me, IDEs provide a lot of useful tools. For example, I love being able to hit a single key to jump to the source definition of a function call. It makes it super easy to trace program flow. ST doesn't do that (ctags plugin doesn't really help).
IDEs can be great when they understand your code well enough to do things like renaming all uses of a function, refactoring, applying code-style formatting, highlighting errors in code (I've caught a lot of errors from co-workers that use ST, while my IDE clearly highlights the bug), etc.
In cases where code is harder to analyze, like JavaScript, IDEs can be far less useful.
Re: Sublime Text 2 plugin to show git commit history for selected line(s) of code
#40Earlier quoted context omitted.
One of the reasons I dislike IDEs is the same as the reason I dislike things like janus or oh-my-zsh, and the same reason that I removed my employer's 'source ...' from my vimrc at work. Poorly considered collections of nonsense that I don't want to be thrust into. Furthermore, I select my plugins carefully with future-proofing as my number one priority. This means that I do not use (or at least certainly do not rely…
I find that take quite interesting considering the rapid pace at which software and computing changes over time. I would expect that by the time I retire in 30 years that nothing that I do right now will exist or be at all relevant. I use certain software right now for programming that is completely different than what I used even two years ago. I work in completely different technology stacks and completely differen…
Vi style editing has lasted entire careers already, and provided "programming" remains at it's core a matter of manipulating text files, I see no reason for it to not last mine. The day the industry transitions to "LabView 2: Electric Boogaloo" is the day I tap out of the industry.
> I actually enjoy switching between various [...] tools
I guess that's the difference between you and I. I don't, at all. I find satisfaction in what I do, not how I do it. Learning new tools for no reason other than I picked the wrong one to learn five years ago and the developers of my old tool packed up shop is something that I think is to be avoided at all costs.
And to be clear, I am more than willing to pick up knew technology that I believe will have significant staying power. Git is an example; whatever version control system that will replace it in 10-15 years will look significantly like it. Git's CLI interface is not an example; I know how to do what I need to do in Git, I know how Git works 'under the hood', and I know how to teach myself the rest on demand, but I do not spend time memorizing the intricacies of the various flags to the various git commands. That knowledge will likely become useless in 10 years or less.