Writing a new text editor with performance in mind, moreso.
Not necessarily, responsiveness is an important consideration for any program, and speed in one area can be used to pay for the parts that are more sluggish.
Eclipse is an interesting case, as in my experience, its autocompletion actually manages to be slower than just typing out the full name in nearly all cases. Certain Java using retards are clearly in need of a good Miller-slap.
Name:
Anonymous2009-10-22 17:08
>>41
For a fucking text editor? Are you kidding me?
Name:
Anonymous2009-10-22 17:35
>>36
Nice and backwards there. The extension language should be fast as these things go so complicated scripts can run well. The editor itself doesn't need to be any faster than the user.
Name:
Anonymous2009-10-22 18:09
Maybe it's for programming languages to become more graphical.
Maybe blocks could be defined with elegant curving lines coming down from the start to the end. there would be no need for braces. the line would define it. also the block could be colored either using defaults for the block type, or custom for particularly special blocks (ZOMG MAIN LOOP) etc.
Name:
Anonymous2009-10-22 18:22
>>44
In other words, the extension language should be fast if you're making Emacs. Most editors are concerned only with user interaction, and not with running scripts.
Ideally, there would be a decent editor built around a dynamic, JIT-compiled language, because Emacs Lisp is just that horrible.
* It has to be as fast as possible, so interpreted languages are out. * You don't want to micro manage memory, so C is out. * You don't want to require programmers to have a degree, so C++ is out. * You want fast startup and not depend on a big runtime, so Java is out. * It has to run on most systems, anything with a C compiler, so D is out. * You want to have fun making something new.
basic / pascal ?
Name:
Anonymous2009-10-23 5:25
>>8
This "Zimbu" language appears to be some ugly bastard hybrid of BASIC and D.
So, I downloaded the Vim package for this egregious language, and it's full of macros to do shit like auto-capitalizing keywords when you type them. Now, the website says part of the reason for uppercase keywords is to allow the user to use the lowercase version as a variable name, but with these macros, you'd have to go back over the word you just typed and lowercase it. (Like this takes any effort at all in Vim....But still.)
What's more annoying to me are the lack of statement terminators It makes the program look like a really long run-on sentence and hard to read
Or maybe they want you to write only one statement per line
But then that's also stupid since you end up
with
lots
of
wasted
space
>>61
80x25 means I can have 2000 characters of code on a single terminal, but FIOC takes it all away. If we coded like FrozenVoid we wouldn't need dual super-wide screen monitors to manage our deeply nested Haskell Monads and Python Duck Types. Think of the billions that could be saved on hardware and energy! FIOC is rapidly destroying the planet right under our noses and no one fucking cares. Is Zimbu the answer, vim the text editor, and FrozenVoid the savior? Only time will tell.
>>64
But there's no dual-screen support on Linux in the first place, and you wouldn't be forced to use vim if you had access to an OS where text editors can have horizontal scrollbars (such as Windows, OS X, Amiga, Menuet, etc.)
Name:
Anonymous2009-10-27 2:11
>>68
Vim is the only editor allowed on Linux because it's the only one without horizontal scrollbars?
P.S. Lol scrolling horizontally to see code. Get a word wrap.
Name:
Anonymous2009-10-27 4:05
>>68
>But there's no dual-screen support on Linux in the first place
OMIGOD IMA BACK IN 90s!
Name:
Anonymous2009-10-27 4:18
>>70
/prog/ IS the nineties. Music, culture, programs, etc.
Name:
Anonymous2009-10-27 4:55
>>71
Nothing good has happened after the nineties. Nothing.