Vim vs Textmate [closed] - macos

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Is text mate really worth it? When there is Vim which is free. I've heard that the Vim learning curve is steep but vi(m) is in almost every *nix os. Which is more powerful and is text mate worth the price tag

Vim is more powerful, and textmate is worth the price tag.
I am pretty convinced that vims modal editing and text objects is the most efficient way to accomplish the task of doing raw text editing. It also take an extremely long time and a lot of effort to get to the point where you are able to say that for yourself. Once you are at the point where the modality is a joy instead of a chore, and you think in terms of text objects, learning things feature by feature is easy. But to get there, I would say 2-3 months if you are putting effort specifically into learning vim, 6-8 months if you are just using it as a normal text editor and absorbing stuff as you come across it. That is an incredably steep investment, and something that a lot of very capable and professional developers don't want to do, which I think is fine. But a certain type of brain actually ENJOYS doing it, and for that kind of person, vim is pretty unbeatable.
Textmate is incredably powerful, with a much more graduated learning curve. So you can start out using it like notepad, and gradually learn more and more shortcuts and more powerful techniques. Someone who is an expert at textmate is extremely fast, and the editor really is a joy to use. It also looks fantastic, even on macvim, I am so jealous of the way code looks in textmate. That being said, 2.0 has been promised for years now without delivery, which has caused a lot of disgruntlement in the textmate community. I would also check out sublime editor on osx if I were in youre shoes and making this choice, not as many people using it, but heard very good things.
TL;DR: vim is amazing and worth the investment, but the investment of your time is pretty substancial. Textmate is worth your money and is an amazing editor that is easy to pick up and learn as you go.

Related

Is there any ghci GUI frontend/extension that support inline graphics display like ipython? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I mean it have features like inline graphics display, worksheet mode, audio playback and ect ... like ipython, maple and matlab
I found winghci on windows but it doesn't seem to have those features. (BTW, I didn't use Windows)
On Linux, I can't find any GUI mode for ghci. I always run ghci from terminal.
Duplicated? this and this show that ghci is capable of do graphics but it is not exactly what I want to know.
There is a Summer of Code project called GHCLive, which looks exactly like what you want.
Quite surprisingly, no one is really talking about it.
I wish they were.
There's no "graphical" version or variant of GHCi. As pointed out in the linked questions, there are plenty of Haskell libraries to do plots, drawings, and other graphics, and there are plenty of libraries that output audio or produce music.
If you just need nicer Haskell programming helpers, you should look at the various Haskell modes for Emacs (my personal favourite is ghc-mod). These also let you evaluate Haskell expression from Emacs, which could allow you to simulate worksheets.
There are also some pure-Haskell editors like Yi or Leksah which do everything the Haskell modes for Emacs do, but in a purer way. In particular, Leksah aims to be exactly what you're looking for: an IDE for working with Haskell.

Should I ignore SCSS? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I consider myself and excellent CSS writer. Lately, I have had some requests to code in SCSS. However, I don't run Ruby in my environment and am weighing whether I should deal with that overhead. And yes, I know there are some work arounds to compile the SCSS.
So, should I go out of my way to learn and support SCSS, or should I consider it strictly a Ruby gem that has nothing to do with what I do?
Further, since most of my work runs goes on LAMP environments, what is the utility unless I have a client running Rails?
The syntax is not that different, and there are online converters that can do the work for you. I would say that you should go for it.
I think scss is a lot better then css. You can write your css file very easy.
Take a look at the website of Sass, there are a lot of examples which are making you writing css much more easier. When you take a look at these, you will see that too.
Here is the link: Sass to the website.
My opinion: go for it!
I also consider myself a fairly proficient CSS (writer? coder?). I've thrown SCSS out the window because I don't see the benefit. Honestly I just don't really understand what problem it solves.
I group it with the similar "coffee". My response to both of those (not necessarily directed towards you) is:
Listen, we don't need more abstraction. Learn Javascript, Learn CSS. You can take those skills with you. Pretty soon we'll just have a one-click button to build our yet-another-blog-system, pat ourselves on the back and call ourselves programmers.
Anyway, I like your thinking. I say flex your CSS muscles and stay in shape :)

Notepad2 or similar editing tools for Mac? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I am switching to a Mac web development environment (esp. Python and Javascript) after using a PC for many years. On the PC, I used Notepad2 for most of my development; a really great minimal drop-in replacement for notepad. It has a very short install and setup process. I did not want code folding, I did not want a tabbed/multi document interface, and I think this lighter editing philosophy works well with interpreted languages. Notepad2 does syntax highlighting and powerful text operations well, plenty of sexy keyboard shortcuts.
Based on this, what kind of editor would you recommend for Mac? I am looking into TextEdit, Textwrangler, and PyCharm so far. Or should I man up and Vim?
I'd highly recommend TextWrangler. Although I was not his best friend at start I just love him now. Very powerful while (at the same time) straight forward and simple. When looking into Vim give MacVim a try (GVim for Mac). If provides a GUI granting you the possibility to keep basic text editor usage pattern like copy&paste (cmd-c cmd-v ...). Comfortable especially when using other ('regular') text editors in parallel.
I'm frequently using both of them.
I use TextEdit on Mac, but I use Vim when I'm in the terminal on Mac. So I'd say do both. Checkout Playterm.org, they have some great Vim tutorials on there.
Textwrangler is okay, but I've found that the RegEx support/usability in TextEdit is superior. That's just me.
I haven't used PyCharm, so I cannot say. As far as Vim goes, it's a tool, and it does take time to learn how to use. That being said, you can use it cross-platform and have access to all of the extras for it. It's also free, whereas TextMate isn't.
I will put in a vote for Sublime Text 2. Very powerful, fast, and extensible.

Advisable to use MFC? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I heard here a lot that MFC is outdated, and wraps Win32 in bad OOP.
But Microsoft released MFC 10 with VS2010, and it has latest tools like ribbon interface, so should one use it for simple apps?
MFC is widely considered to be poorly designed but it has been updated recently and appears to be alive and well. You may decide not to use it for other reasons, but you should not reject it for being outdated.
MFC doesn't look bad if you understand it. Otherwise you consider it as poorly designed.
MFC is not outdated: a lot of complex applications use MFC, for example MS Office. And you even can find in samples how to make office-look application.
Also for simple apps you can use ATL.
I have seen MFC applications are noticeably faster, particularly they load faster compared to C#. The compelling arguments I have heard from C# guys are it is very fast to development in compared to MFC. In terms of performance MFC wins hands down.
You can make a call on what kind of application you are developing and what features do you need. The trend unfortunately is moving away from MFC though I personally can't justify it. I know couple of companies who are planning to migrate MFC applications to .NET My friends there old me mainly it's the faster development time and it is easy to develop in.
If you are bold you can still start new application with MFC and do better than those who would with C#. If you just want to go with trend than use new easier tools and take a little hit with performance.
Overall I would definitely not sideline MFC as it might be the only fit for certain high performance applications. For example I love the GUI threads in MFC which don't exist in C++ but are very powerful if used properly. I don't know if they exist in C# or newer languages but I wouldn't like to give up on them.

Text-Based User Interface Development [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Where can I find resources related to the design and development of text-based user interfaces (e.g. interfaces exported via serial port from embedded devices to VT100 terminals)? I am interested in any material available - best practices, style guides, frameworks, etc.
Note that I am asking about resources related to the design and development of 'TUIs' rather than command-line interfaces (the thrust of Text User Interface Design Reference?). Wikipedia differentiates TUIs from CLIs (and GUIs) as follows:
TUIs are different from command-line
interfaces in that, like GUIs, they
use the entire screen area and do not
necessarily provide line-by-line
output. However, TUIs only use text
and symbols available on a typical
text terminal, while GUIs typically
use high-resolution graphics modes.
I don't have any experience with VT100 and that kind of stuff, but I know that Turbo Vision is still around and kicking on quite a few platforms, DOS and Linux included. And back in its day, it was used to write some of the better TUI applications (Borland C++ and Borland Pascal DOS IDEs come to mind), and I've seen it used in LOB applications back then quite often as well.
Screenshot:
(source: sourceforge.net)
Perhaps take a look at ncurses? It's a GNU library specifically designed for writing terminal-based UIs.
For best practices and style guides, the IBM Common User Access (CUA) defines a "text subset" that should be helpful especially if your users are used to GUIs. Details are in Chapter 3 of:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/F29BDG00/CCONTENTS
Additional CUA guidelines and standards are in:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/F29AL000/CCONTENTS?DT=19921204095534
http://petesqbsite.com/sections/express/issue21/tuiseriespart1.htm
http://en.wikipedia.org/wiki/Text-based_user_interface
Hope it helps... I still make programs in TUI (www.harbour-project.org)

Resources