We are rewriting CodeMirror • Hacker News Board

Re: We are rewriting CodeMirror

#31

Post by [deleted] » Tue, Aug 28, 2018, 7:51 PM UTC

brainkim wrote: post #10

marijn wrote: post #2

Oh hi, I'm Marijn, one of the maintainers. It doesn't look like this submission is going anywhere, but I'll keep an eye on the comments and respond to questions.

I’m currently in the process of writing a codemirror mode for a language I’m working on, is the way codemirror modes are written/used gonna change substantially? Should I hold off on this work? I’m glad to see you’re focusing on accessibility!

[deleted]

Re: We are rewriting CodeMirror

#32

Post by marijn » Tue, Aug 28, 2018, 7:53 PM UTC

msoad wrote: post #20

tokyodude wrote: post #18

I have to ask what is probably a dumb question. Why? I used CodeMirror on three projects. It was great. Now I use Monaco aka Visual Studio Code. What would CodeMirror offer ? With Monaco I get all the lastest feature of VSCode . Current versions of Monaco include Intellisense etc.. I'm honestly curious both what CodeMirror will offer and why even try to compete. Though I'm guessing the answer to the first question an…

I welcome competition in this space but two guys competing with Microsoft seems like impossible to win. Hopefully they get the funding and we can see what they can build

They are not putting _that_ much energy into Monaco, and these are not terribly huge systems. Also, I've been doing this for ten years, so that helps, in terms of experience.

Re: We are rewriting CodeMirror

#33

Post by marijn » Tue, Aug 28, 2018, 7:58 PM UTC

undershirt wrote: post #16

I didn't know what beautiful JS code looked like until I started reading CodeMirror while debugging an issue. After reading through Atom's code, I was really surprised how simple CodeMirror's code was—with minimal abstractions and flat functions. (donated, of course)

Thanks! It's going to get a little more abstract in v6 (but only where the abstractions carry their weight).

Re: We are rewriting CodeMirror

#34

Post by marijn » Tue, Aug 28, 2018, 8:00 PM UTC

GoToRO wrote: post #13

Can it edit the files on a server directly or you have to do that part yourself? Or are there any projects that I could self-host and let me edit the files on a server folder? Thanks.

You have to do that yourself—this is only the editor component. There's things like https://icecoder.net/ that provide a more web-ide like thing on top of CodeMirror, but I don't know them intimately so I don't know which one to recommend.

Re: We are rewriting CodeMirror

#35

Post by bealuga » Tue, Aug 28, 2018, 8:16 PM UTC

Ah I loved code mirror! I ended up using it in one of my projects called picoshell here which was an in-browser code editor. https://www.youtube.com/watch?v=6ubEwT6igZQ

Re: We are rewriting CodeMirror

#36

Post by marijn » Tue, Aug 28, 2018, 8:27 PM UTC

skybrian wrote: post #12

marijn wrote: post #2

Oh hi, I'm Marijn, one of the maintainers. It doesn't look like this submission is going anywhere, but I'll keep an eye on the comments and respond to questions.

I'm curious if you learned anything from studying monoco-editor from VS Code? Do they use a different approach?

I did study Monaco, but we're using a very different approach (Monaco resembles the current CodeMirror more), because what they do in almost impossible to make work on mobile. When it comes to accessibility, they do a great job, and I'm planning to take more inspiration from their code as I work on things like autocompletion

Re: We are rewriting CodeMirror

#37

Post by todd3834 » Tue, Aug 28, 2018, 8:29 PM UTC

msoad wrote: post #20

tokyodude wrote: post #18

I have to ask what is probably a dumb question. Why? I used CodeMirror on three projects. It was great. Now I use Monaco aka Visual Studio Code. What would CodeMirror offer ? With Monaco I get all the lastest feature of VSCode . Current versions of Monaco include Intellisense etc.. I'm honestly curious both what CodeMirror will offer and why even try to compete. Though I'm guessing the answer to the first question an…

I welcome competition in this space but two guys competing with Microsoft seems like impossible to win. Hopefully they get the funding and we can see what they can build

It is possible that less than 2 people at Microsoft are working on Monaco full time but just getting passive improvements over time. Never underestimate 2 smart dedicated engineers.

Re: We are rewriting CodeMirror

#38

Post by Scarbutt » Tue, Aug 28, 2018, 8:37 PM UTC

marijn wrote: post #2

Oh hi, I'm Marijn, one of the maintainers. It doesn't look like this submission is going anywhere, but I'll keep an eye on the comments and respond to questions.

Why typescript? wouldn't that choice reduce the number people that can contribute?

Re: We are rewriting CodeMirror

#39

Post by undershirt » Tue, Aug 28, 2018, 9:26 PM UTC

marijn wrote: post #33

undershirt wrote: post #16

I didn't know what beautiful JS code looked like until I started reading CodeMirror while debugging an issue. After reading through Atom's code, I was really surprised how simple CodeMirror's code was—with minimal abstractions and flat functions. (donated, of course)

Thanks! It's going to get a little more abstract in v6 (but only where the abstractions carry their weight).

i'm sure the abstractions will increase out of necessity. it was just nice for once to warily peek into the code of a great product and see a single, well organized ~9k line file of small functions that I could follow with relative ease. best wishes on the new version!

Re: We are rewriting CodeMirror

#40

Post by marijn » Tue, Aug 28, 2018, 9:39 PM UTC

Scarbutt wrote: post #38

marijn wrote: post #2

Oh hi, I'm Marijn, one of the maintainers. It doesn't look like this submission is going anywhere, but I'll keep an eye on the comments and respond to questions.

Why typescript? wouldn't that choice reduce the number people that can contribute?

It provides significant advantages when it comes to noticing bugs and including types (also for docs) in the code from the start. I feel that TypeScript is widely enough known at this point (and close enough to JavaScript to figure it out quickly) to not be too much of a barrier.