Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Xray – An experimental next-generation Electron-based text editor

github.com

Post reply on HN
Print view View original

41–50 of 240 posts

Re: Xray – An experimental next-generation Electron-based text editor

#41

Post by kjksf »

stouset wrote: post #34
codedokode wrote: post #30

Also, I noticed that it requires WebGL so without modern and supported by WebKit graphic card it won't work. Why is OpenGL necessary for a text editor? I don't understand.

Hardware acceleration of rendering is more energy-efficient and less resource intensive than CPU-based software rendering.

The way XRay render text is more compositing than rendering.

They will render text to a bitmap using HTML canvas and then use that as a texture for GPU.

GPU will be compositing those bitmaps, it won't actually be rendering text.

Re: Xray – An experimental next-generation Electron-based text editor

#42

Post by PrimHelios »

Prefinem wrote: post #23
bluedino wrote: post #21

Earlier quoted context omitted.

What's the memory footprint of Terminal.app and vim + plug-ins?

Not sure, but I have had vim lock up my MacBook Pro with 16GB of RAM and force me to do a hard reboot

That sounds like an OS/hardware problem, honestly. There's no reason vim with any setup should lock up a machine.

Re: Xray – An experimental next-generation Electron-based text editor

#43

Post by amingilani »

I always felt like the Atom team should scrap their work and start afresh. I love Atom, and have used it as my primary editor since its inception, but it's been the worse performing text editor I've ever encountered.

I almost switched to Vim a few months ago, but the impact to my performance was too high for me to keep it up for long enough.

I'm definitely going to be using Xray the moment it becomes stablish.

Re: Xray – An experimental next-generation Electron-based text editor

#44

Post by bryanlarsen »

codedokode wrote: post #30

Also, I noticed that it requires WebGL so without modern and supported by WebKit graphic card it won't work. Why is OpenGL necessary for a text editor? I don't understand.

I'm sure that software rendered webgl will be fine unless you're running a 5k monitor. It's just being used as a convenient texture glitter, the primary benefit is bypassing the DOM.

Re: Xray – An experimental next-generation Electron-based text editor

#46

Post by zero_iq »

ahtu123 wrote: post #17
toomanybeersies wrote: post #5

I've always felt like the inevitable conclusion of Atom and other electron based apps is the reversion to using low level compiled languages. I'm starting to get tired of how much of a resource hog Atom is.

I'm always amazed when I see the size of the Atom executable on my computer(438MB). It's the size of a game! It's also pretty much the worst performing text editor (in runtime for most operations) and a memory hog. I really don't get the hype.

I always think back to when I had a 120MB hard disk in the early 90s. It contained multiple editors, raytracers, games, music editors + music, images, paint programs, multiple programming languages and development kits, a multi-tasking operating system... and room to spare.

90s me would be absolutely floored by a text editor needing 438MB RAM.

Wait, what am I saying? 2018 me is pretty flabbergasted by it, but perhaps less surprised (and more cynical) than 90s me.

Re: Xray – An experimental next-generation Electron-based text editor

#48

Post by Prefinem »

PrimHelios wrote: post #42
Prefinem wrote: post #23

Earlier quoted context omitted.

Not sure, but I have had vim lock up my MacBook Pro with 16GB of RAM and force me to do a hard reboot

That sounds like an OS/hardware problem, honestly. There's no reason vim with any setup should lock up a machine.

The linter was the issue.

I actually have better performance with Sublime Text and JavaScript than I do with vim and JavaScript. I wish that weren’t the case.

If you know if any better ways to get vim working with Syntastic for linting (eslint), I would love to know.

Re: Xray – An experimental next-generation Electron-based text editor

#49

Post by ehsankia »

ahtu123 wrote: post #17
toomanybeersies wrote: post #5

I've always felt like the inevitable conclusion of Atom and other electron based apps is the reversion to using low level compiled languages. I'm starting to get tired of how much of a resource hog Atom is.

I'm always amazed when I see the size of the Atom executable on my computer(438MB). It's the size of a game! It's also pretty much the worst performing text editor (in runtime for most operations) and a memory hog. I really don't get the hype.

As with most things when it comes to software engineering, it's just a trade-off, and depending on your use case, you may fall on either side of it. They sacrifice memory usage for development pace. Using Javascript/CSS allows them to not only get some of the most powerful pre-existing tools, but also allows the 3rd party community to move at a much faster pace too. Atom already has twice the number of packages as Sublime Text while being half the age.

Re: Xray – An experimental next-generation Electron-based text editor

#50

Post by regnerba »

amingilani wrote: post #43

I always felt like the Atom team should scrap their work and start afresh. I love Atom, and have used it as my primary editor since its inception, but it's been the worse performing text editor I've ever encountered. I almost switched to Vim a few months ago, but the impact to my performance was too high for me to keep it up for long enough. I'm definitely going to be using Xray the moment it becomes stablish.

Any reason you haven't tried visual studio code?
Post reply on HN