Our great sponsors
-
brackets
An open source code editor for the web, written in JavaScript, HTML and CSS. (by brackets-cont)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
hydrogen
:atom: Run code interactively, inspect data, and plot. All the power of Jupyter kernels, inside your favorite text editor.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
textadept
Textadept is a fast, minimalist, and remarkably extensible cross-platform text editor for programmers.
-
nw.js
Call all Node.js modules directly from DOM/WebWorker and enable a new way of writing applications with all Web technologies.
-
SubEthaEdit
General purpose plain text editor for macOS. Widely known for its live collaboration feature.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Why not collaborate with developers of existing code editors such as Xi Editor (https://xi-editor.io) or Lapce (https://lapce.dev) instead of making yet another one?
As for lightweight alternatives to Atom, there is also Lite-XL (https://lite-xl.com).
What was Atom good for, when compared with something like Visual Studio Code?
I recall reading about typing latency and it seemed to come out as one of the slower options: https://pavelfatin.com/typing-with-pleasure/
I guess it would have occupied a similar place as Brackets, another vaguely similar project? https://brackets.io/
Then again, with how popular VSC has become and with how insanely many extensions there are for it, using any other editor feels a bit... counterproductive at times?
Personally, i'm using the following:
- CLI: nano (vim works too, I just like the simplicity more)
Why not collaborate with developers of existing code editors such as Xi Editor (https://xi-editor.io) or Lapce (https://lapce.dev) instead of making yet another one?
As for lightweight alternatives to Atom, there is also Lite-XL (https://lite-xl.com).
I personally found Atom + Hydrogen [0] to be the most productive interactive Python environment I've ever used. I really want to see VSCode adopt some way to run a Jupyter kernel for a Python file (with a notebook UI) and have rich results in line with the code (i.e. not a terminal output off to the right side of the screen).
[0] https://github.com/nteract/hydrogen
Earlier this year Keith Simmons, the author of Neovide (https://github.com/neovide/neovide), joined our team. He's been working on Vim bindings and paying a lot of attention to getting it right. As you probably know there's a lot of surface area, so this will take time.
How does it do in comparison to the other upcoming "better VSC"s? Like for example:
https://v2.onivim.io/
https://helix-editor.com/
Textadept has both TUI and GUI, and is Free Software: https://orbitalquark.github.io/textadept/
The way it works is that its creator made a TUI implementation if the GUI library he used for the graphical version, so you have the same menus etc.
He doesn't. Linus uses MicroEMACS [0], which is an entirely different editor that uses emacs bindings.
It's not the lisp machine that incidentally happens to edit code that GNU Emacs is.
Or, as he puts it [1]:
> I use this abomination called "micro-emacs", which has absolutely nothing to do with GNU emacs except that some of the key bindings are similar.
[0]: https://github.com/torvalds/uemacs
Why not collaborate with developers of existing code editors such as Xi Editor (https://xi-editor.io) or Lapce (https://lapce.dev) instead of making yet another one?
As for lightweight alternatives to Atom, there is also Lite-XL (https://lite-xl.com).
There is also NW.js (f.k.a. Node-Webkit), which was preceding Electron and was also a foundation for a lot of apps: https://github.com/nwjs/nw.js/wiki/List-of-apps-and-companie...
Oh, that's a good point about the sunsetting. In Brackets's case, Adobe left it active in the hands of the community.
Live Preview in particular is one of the areas I had some fun working on. I worked out a way to do diff/patch to make it quickly and incrementally update the browser[1]
[1]: https://github.com/adobe/brackets/wiki/Research%3A-HTML-DOM-...