Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.

A Look at Vim, a Text Editor for the Ages

posted by chromas on Wednesday August 22 2018, @09:22PM   Printer-friendly
from the :wq dept.

hubie writes:

Over at The New Stack is a brief but entertaining history of the editor vi and Vim.

"The editor was optimized so that you could edit and feel productive when it was painting slower than you could think. Now that computers are so much faster than you can think, nobody understands this anymore," Joy said. "It was a world that is now extinct. People don't know that vi was written for a world that doesn't exist anymore."

Original Submission

 
This discussion has been archived. No new comments can be posted.
A Look at Vim, a Text Editor for the Ages | Log In/Create an Account | Top | 135 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by Alfred on Thursday August 23 2018, @01:24PM (1 child)

    by Alfred (4006) on Thursday August 23 2018, @01:24PM (#725194) Journal
    Where does the only Xcode policy fit into the story?
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 2) by MichaelDavidCrawford on Thursday August 23 2018, @05:13PM

    by MichaelDavidCrawford (2339) Subscriber Badge <mdcrawford@gmail.com> on Thursday August 23 2018, @05:13PM (#725275) Homepage Journal

    It's been using the Cocoa Text Widget for most of its existence.

    I'm pretty sure Project Builder's editor wasn't NeXT's NextStep Text Widget.

    That ThinkC really _was_ so very responsive I'm quite certain was the result of its editor being written in 68000 assembler. I expect CodeWarrior's was written from the start in C. I didn't use Symantec enough to really tell the difference.

    It's only been since late 2016 that I've regarded Xcode's text editor as anything other than Hammering Nails With My Fists. And yes I've always ensured that _everybody_ in Apple's Tools Group knows what I think of - specifically - their text editor.

    Using Xcode on my Mid 2015 MacBook Pro actually works quite well; however back in 2015, to have used the 2015 version of Xcode would not have worked well.

    The difference is that Apple places an exceedingly high priority not so much on any of its widgets' performance but they do place quite a high priority on tuning the code that the widgets are built on top of.

    That Mac OS X binaries always have the Mach-O Executable Format is specifically so that Method Lookups only need the address of the C string with the method name. Linux and I expect BSD can run Cocoa programs but their method dispatch does string comparisons rather than 64-Bit integer comparisons.

    I don't know much about The Cocotron [cocotron.org] for Win and Linux other than that Andy Green [em.net] really likes it.

    --
    Yes I Have No Bananas. [gofundme.com]