I was waiting for the punch line
Fine, I'll build my own text editor
241–250 of 264 posts
Re: Fine, I'll build my own text editor
#242Earlier quoted context omitted.
Don't forget the post score is a balance of up votes and down votes. This mean 2 down votes and 0 up votes registers the same (-1) as 10 down votes and 8 up votes (-1). So there's no sense treating it like the community has forsaken you.
I'm pretty sure that downvotes from some users, perhaps those at a given karma threshold, count twice. I've seen quite a few posts that aren't otherwise attracting a lot of attention go straight from 1 to -1 more-or-less instantly, or from 3 back to 1. It's also possible that they have experimented with fuzzing votes like Reddit does. Either way, they don't seem inclined to disclose how it works behind the scenes. Th…
Indeed, I'm basing my statement on observation, I don't think they've ever disclosed exactly how the math works.
Re: Fine, I'll build my own text editor
#243[flagged]
Re: Fine, I'll build my own text editor
#244Earlier quoted context omitted.
I use Emacs and the edits I do seem imperceptible to me. Do you know of any test I should try to see whether the lag is notable and intrusive? Emacs does start fairly slowly, though, takes about 0.6 seconds.
I would love to see your config!
Okay, including comments it's about 1,200 lines https://codeberg.org/tmtvl/open-dotfiles/src/branch/main/ema...>. My user-lisp directory contains Daredevil SKK, Groovy mode, and ICL; those are all available on Microsoft GitHub.
Re: Fine, I'll build my own text editor
#245The single most disappointing fact about (more or less) all text editors on the market today is how god awful their performance is. For most text editors, and when I say most I really do mean _most_, you can very easily start seeing noticeable lag and stuttering when making modifications, or even outright INPUT LAG when entering text. For very tiny buffers 1MB, 99% of them are unusable due to a) writes taking SECONDS…
[flagged]
Re: Fine, I'll build my own text editor
#246I still miss NEdit. Around 2001 when I started getting into Linux seriously, I was also reading a lot about cults - Scientology had recently, infamously, forced Slashdot to take down a comment about their secret practices. One of the things I read was that a common cult trick was to demand that people re-learn basic skills so that they do them the "right" way, like reading (Scientology did that), eating (chew X times…
Hey, greetings from another former nedit user. It was my refuge from emacs on my 1997 redhat setup as I was stumbling around learning the ropes (I had to keep referring To my "Linux in a nutshell" book to remind myself how to open, save & quit in emacs)
Nedit was a godsend, until I decided to look into that other weird editor (vim) that I kept hearing about (circa 1999 or so) ...
Re: Fine, I'll build my own text editor
#247Yes, who would have guessed that the element, designed specifically for this use case and built into browsers for 3 decades, would be the most performant and behaviorally consistent way to implement editable text. I'm kind of sad the author stopped shedding unneeded complexity there though... we're not really building a text editor yet, we're building a website with a fancy input field. If we want to build a proper t…
So we take a web browser and trim it down to only ever show a single element you say? That's what I'm taking away from this. All the hard work for accessibility is already done then right?
[dead]
Re: Fine, I'll build my own text editor
#248Earlier quoted context omitted.
I would love to see your config!
Okay, including comments it's about 1,200 lines https://codeberg.org/tmtvl/open-dotfiles/src/branch/main/ema... >. My user-lisp directory contains Daredevil SKK, Groovy mode, and ICL; those are all available on Microsoft GitHub.
Thanks. I was looking for a way to reduce my startup times because I was envious of Neovim. It doesn't work for me out of the box (I'm on macOS now), but it seems that there is a lot to steal from. ;)
Re: Fine, I'll build my own text editor
#249Earlier quoted context omitted.
Sounding and being are not the same thing. I don't want to insult Mr. Pike and claim he is a dick just because how some of his quotes sound.
> Sounding and being are not the same thing. I'm familiar with his stated opinions regarding both generics, and syntax highlighting. They check both the "sounding" and "being" boxes quite nicely.
Dude has worked on UTF-8, Plan 9, and a very popular language despite its flaws.
I am not accomplished enough to judge him. Nor have I had the pleasure to meet him in person to pass any judgement.
I don’t get this obsession with tone policing, probably borne of corporate tendency towards blandness and inoffensiveness. The vast majority of interesting people are eccentric and with their unfiled corners, it’s part and parcel of being outstanding in your field.
Re: Fine, I'll build my own text editor
#250Text editors are like mechanical watches or fountain pens. There is just so much beauty in the machinery that makes them. For me, there are hardly any other modules that are this satisfying to watch being made. Each time I find a new one (a good one like this), with everything on ropes and rendering and I-beam placement computations and ... it feels like a Christmas gift.
Yes, but... On one otherwise tranquil morning Master Foo's meditations were disturbed by cries of distress. Finding that they came from one of the novices, he inquired "What is the difficulty here?" The novice replied, "I am frustrated by my tools. Every day I must use many different editors because neither Emacs nor vi nor any of these other random editors has all the features I require." Master Foo nodded. "How," h…
There are two possibly conflicting lessons from this koan:
a) the world doesn’t need another editor
b) if you build an editor, it should have an intended audience of one: yourself.