News for hackers. Stuff that matters.
Re:Easily Review Comments in Atom – The GitHub Blog by azhenley on Monday April 15, 2019 @06:43PM (#19669565)
I agree that it is strange.

I use VS Code for coding but my students apply their research to Atom plugins since it is much more hackable. If only they would open VS Code up a bit more...

Re:Easily Review Comments in Atom – The GitHub Blog by deadcat on Monday April 15, 2019 @07:57PM (#19669928)
Vscode is perfectly hackable and open, can you be more specific?
Re:Easily Review Comments in Atom – The GitHub Blog by azhenley on Monday April 15, 2019 @08:25PM (#19670052)
From what I have tried, VS Code doesn't allow access to the DOM or give much of an API to modify the visual layer. This makes it very difficult to draw visualizations on top of the editor. It also does not allow plugins to go beyond the standard tab-document metaphor.

For example, students of mine tried to re-implement Patchworks [1] as a VS Code plugin. Didn't seem feasible. They have been very successful in building it in Atom though. As another example, I tried to make a tool that displays a call graph visualization on top of the editor [2]. But again, this was easy in Atom but I couldn't figure it out in VS Code.

Please point me to any documentation or examples of how to implement features like those.

[1] https://youtu.be/GwcxDZT3pXE

[2] http://web.eecs.utk.edu/~azh/pubs/Henley2018bDissertation.pd... Figure 36

Re:Easily Review Comments in Atom – The GitHub Blog by namelosw on Tuesday April 16, 2019 @01:19AM (#19671309)
It's quite hackable but not like Atom or Emacs.

You can find some plugins that could make Atom seems completely different, but most of the VSCode image you can find on the internet remains similar.

Just like with Emacs you can rewrite Emacs itself. And all of the changes in Atom do not require restarting, while some of the VSCode plugins require to restart the code editor (but might explain a little bit why VSCode is faster).