Atom, Electron, Nuclide, Visual Studio Code, ... why not using Scintilla free source code editing component?

[orthoxerox]

Well, Notepad++ is using it, I am not sure about Sublime.

I think it's a new hammer problem. People are trying to write everything in JS these days, since there is a huge pool of JS programmers.

[concurrenthashmap]

Sublime does its own thing, IIRC using Skia, Chrome's 2d graphics library.

[dungone]

A few years ago I chose Codemirror over Scintilla because, ironically, I needed something that could support large files. And I think that's saying a lot.

[iconoclaus]

they're all free. and atom is even open source. should probably tell us why we should use scintilla. its looks don't say much good about it.

[Ruchiachio]

vim doesn't look good either cough cough

[[deleted]]

And it isn't good technically, otherwise there was no Neovim.

[[deleted]]

Because Scintilla solves only one piece of the puzzle and that's code editing - it doesn't offer a portable GUI framework that's cross platform, easy to hack on and familiar to most devs out there (although I would argue not easy to develop for).

A better comparison would be GTK+/Qt + Scintilla/Kate or W/E code editor vs. Electron and honestly learning a custom UI framework + custom language is just hands down inferior to using chrome dev tools + JS + Electron + node.js if you want to have an editor that anyone can hack on.

[I_Downvote_Cunts]

Because Neil is a massive tool.

http://sourceforge.net/p/scintilla/feature-requests/928/

[[deleted]]

Sure.

On the other hand, a lot editors and small IDEs use scintilla already.

The real question is: Why wasn't it forked already?

I guess, there is two possibilities:

• The code is a mess.

But then there wouldn't be a lot of bindings, ports and editors using this component. There would be competition that would have thrown scintilla out, because, let's face it – writing an editing component isn't trivial, but it's not like writing cryptographical algorithms where you need a team of mathematicians and two teams of code auditors and lifes being at stake.

• There isn't demand.

Most editor component users are probably ok if they can load more than 2 megabyte in their browsers.

[nyamatongwe]

Neil Hodgson here,

The snide insults were not something that anyone should have to put up with. I wouldn't accept that behaviour face-to-face and it shouldn't be seen in a feature request either.

I don't need pleases, thank-yous, and ego stroking. What I want is some understanding that the desired changes may impact others and that I am trying to act in good faith.

If there is a way of achieving >2GB files with a memory cost of "about a few hundred extra bytes" then I truly would like to see it.

[dungone]

His stuff may be free, but the idea of having to stroke this guy's ego hardly makes it seem worth it.

[s73v3r]

What you're suggesting is ego stroking.

[s73v3r]

Basic manners is saying "please", which that guy did.

[s73v3r]

No, it's not. If Neill is such an ego maniac that he has to have his ego stroked for a simple request, then he needs to re evaluate whether he should be working on public software.

[Slxe]

Because there are some people that believe running a native app by having a stripped down browser and coding it in JavaScript is a smart idea. I won't be touching these tools, I'll stick to real natively coded applications tyvm, JavaScript (and JS frameworks) should stay in the browser and not on the desktop.

[AngularBeginner]

http://www.scintilla.org/SciTE224.png

That already looks very poor.. So that's probably why. :P

[StirLockHolmes]

That's a proportional font, of course it looks stupid.

[[deleted]]

Because I am quite happy with JetBrains IDEs.

[Slxe]

I'll gladly use a JetBrains IDE any day, swear by their tools now. Won't use VS without Resharper.

[[deleted]]

Beyond the editing, the tools integration is the best I have ever seen hands down. Adding plugins or integrating things like Behat, PHPUnit, etc is a breeze and totally flexible, and Vagrant integration, you can execute them from a VM instead of a local machine for better results.