Guerra degli editor (Italian Wikipedia)

Analysis of information sources in references of the Wikipedia article "Guerra degli editor" in Italian language version.

refsWebsite
Global rank Italian rank
1st place
1st place
1,669th place
2,511th place
1,475th place
1,172nd place
low place
low place
low place
low place
3,959th place
4,340th place
low place
low place
low place
low place
551st place
729th place
1,254th place
411th place
383rd place
1,090th place
low place
low place
low place
low place
low place
low place
low place
low place
6th place
8th place
1,216th place
2,160th place
259th place
549th place
low place
low place
67th place
143rd place
low place
low place
low place
low place
low place
low place
3rd place
14th place
low place
low place
low place
low place

apple.com

developer.apple.com

aquamacs.org

archive.org

  • Larry Ullman, Modern JavaScript: Develop and Design, Peachpit Press, 2012, pp. 64-65, ISBN 978-0-13-290587-9.
    (EN)

    «Text editors require fewer hardware resources to run – disk space, memory, and processor activity, meaning they are better choices if you have an older computer. In fact, the most basic text editors, such as vi and emacs have no graphical interface.»

    (IT)

    «Gli editor di testo richiedono meno risorse hardware – spazio su disco, memoria e attività del processore, quindi sono una scelta migliore per chi ha un computer datato. Di fatto, gli editor di testo più basilari come vi e emacs non hanno un'interfaccia grafica.»

books.google.com

catb.org

  • The Right Size for an Editor, su catb.org. URL consultato il 1º dicembre 2014.
  • Choosing an Editor, su catb.org.
    «these two editors express sharply contrasting design philosophies, but both are extremely popular and command great loyalty from identifiable core user populations. Surveys of Unix programmers consistently indicate about a 50/50 split between them, with all other editors barely registering.»

cmdlinetips.com

emacswiki.org

ergoemacs.org

franz.com

fsfeurope.org

github.com

gnu.org

gnu.org

elpa.gnu.org

  • undo-tree-readme.txt (TXT), su elpa.gnu.org.
    «The only downside to this more advanced yet simpler undo system is that it was inspired by Vim. But, after all, most successful religions steal the best ideas from their competitors!»

guckes.net

linuxhelp.blogspot.com

medium.com

opensourcehacker.com

  • Never use hard tabs, su opensourcehacker.com.

    «Due to legacy, different text editors treat hard tabs different. UNIX text editors prefer hard tab is 8 spaces, Windows text editors and IDEs (Eclipse) prefer that a hard tab is 4 spaces. Thus, hard tabs may break source code readability and editability if there is more than a single person editing the file. They will open the file in an editor with different tab settings, edit it and next time you open the file it is ruined and all indentations are wrong. This is even worse on white space sensitive languages (Python, CoffeeScript) as this might actually cause syntax errors or programming logic errors. However, you can avoid this problem in the first place if you do indentation using soft tabs (spaces) instead. Even if you were the single person in the world editing the text file, even you might switch the text editor in some point and accidentally shoot yourself in the leg.»

slate.com

  • The Oldest Rivalry in Computing, su slate.com.
    «two rival programs can stake a claim to being among the longest-lived applications of all time. Both programs are about to enter their fifth decades. Both programs are text editors, for inputting and editing code, data files, raw HTML Web pages, and anything else. And they are mortal enemies.»

sourceforge.net

vimdoc.sourceforge.net

stallman.org

theregister.co.uk

udemy.com

unix.com

upsilon.cc

vim.org

web.archive.org

wikia.com

vim.wikia.com