I can't stand when you're expected to wrap every sentence in some sugar coated fake 'niceness' just to not step on somebody's toes. If I have a certain way of expressing myself... Well that's how it is.
It doesn't have to be about sugar coating. Just try to take some of the emotions out of the conversation and stick to stating the facts, and you can easily come across as much less offensive.
>> If I have a certain way of expressing myself... Well that's how it is.
You shouldn't sell yourself short. Changing the way you communicate is a huge but worthwhile challenge.
In a different time, I would have been mean to you over your comment instead of offering supportive words. It took as much effort to be nice as it used to take to be mean.
Emacs have been my main editor for 15 years soon and while it definitely got some rough edges, once you learn all basic key-combinations for editing and buffer management (which often is even more uncomfortable with a non us keyboard layout) I feel that nothing else really compare. Text editing is great but as many have pointed out the extensibility and all the high quality community projects/modes out there make emacs something unique. I don't think it's wrong to regard emacs more as an elisp environment than an editor.
The biggest problem with emacs right now as I see it is the lack of multi-threading.
I think that's a poor excuse for not having a linux version. By that logic, we wouldn't have sublime because vim/emacs should be enough.
As I see it, the main reason I like to use linux on my development boxes is flexibility(or call it freedom if you want, I don't like doing so). I can do things in whatever way works best for me and I can create scripts/install packages to glue stuff together fairly easily to adapt to my workflow.
That was rather my point. It's not that Linux doesn't need UIs because their users all use CLIs, it's that it's users all user CLIs because anyone who'd like a nice UI stays well away.
I never said anything about removing existing software (such as sublime). I was talking about there being less incentive to create a git gui for a user base that is - from my experience - happy with the current cli interface or any other already existing client (such as magit for emacs).
You should use enums for singletons i Java. Simple to write, threadsafe and handles serialization. All with guarantees from the Java language specification.
I wasn't actually talking about singletons, just the doublechecked locking pattern. It's also necessary for laziness on objects that are referenced by multiple threads.
I tend to think Singletons are a dubious design pattern, like a lot of other people.