Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2022-02-28

Channels

#editors
<
2022-02-28
>
mauricio.szabo19:02:47

Just for the record: it is possible to reuse fragments of Atom and VSCode to create a hackable new experience - one that may be compatible with most of Atom and most of VSCode API, but without the same limitations and maybe ways to define custom commands, change CSS, better keybindings, etc. I'm still not sure if I'll continue this experiment, but though it was worth sharing it here

pez20:02:46

So awesome. And a lot of work ahead there. 😀

mauricio.szabo14:03:50

@U0ETXRFEW I will only continue if I can savage parts of other editors and use them without any change at all, otherwise yes, it's too much work :rolling_on_the_floor_laughing:

orestis15:03:41

This is very interesting - there's the issue of having the lowest denominator though...

mauricio.szabo03:03:27

I'm not sure what you meant about the lowest denominator thing. The idea is to support 90% of Atom and VSCode extensions, while making the editor as hackable, or maybe even more, than Atom itself. Again, I'm aware that's lots of work, but the idea is not be tied to what both editors support only...

orestis07:03:24

Oh then it's the reverse, right? You'd be providing e.g. "all" the extension points of VSCode API + the extension points of Atom. I thought you were aiming for the common ground.