Live data from Hacker News

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

github.com

91–100 of 240 posts

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

#91

Earlier quoted context omitted.

Any reason you haven't tried visual studio code?

Can't speak for op of comment, but everyone suggests this... yes I've tried it and no I really don't want it no matter how many times it is mentioned. I am happy with Vim for myself now, and am glad that I moved beyond the bloated IDE way of thinking, including Visual Studio Code. Yes, Atom had its shortcomings in that arena, but I'd still prefer to use Atom over Visual Studio, due mostly in fact that the project has…

You're a bit late to the party lol. vim is dead.

All us 'cool elite programmers' as you so blindly follow, have moved onto to use neovim.

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

#92
post #17

Earlier quoted context omitted.

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've had Atom taking up 1.5 GB before. Right now Spotify is taking up 1 GB. VLC can play 4k with less RAM, what the hell?

Try 10GB each for Illustrator & Photoshop CC :(

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

#93
post #57
post #6

How disappointing that text editors require such... abstraction. Overengineering at its finest?

Let's see if someone able to code complex application only using Notepad.

It's better than Edlin. That was my first text editor.

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

#94

Earlier quoted context omitted.

Agreed.... running Slack + Atom + Chrome is enough to kill a I'm on emacs and firefox for good.

Firefox has started sucking battery like crazy for me in the last few days, though. Can't figure out what it is.

Are you on a Mac? Had same, but fixed it with some prefs changes. Before that FF was stuck at 8-10% CPU.

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

#96

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.

The v8 engine behind Atom is an incredibly efficient compiler, a just-in-time compiler. Without it, all current JS interfaces would be comically slow.

The problem with JS is that its execution model is built around highly dynamic features that are hard to compile efficiently. It also lacks a nice type system, though Typescript helps a lot.

The problem with Atom performance, I suspect, is mostly with its using a web browser and DOM to exit text. I bet that elisp is seriously slower than JS on v8, but Emacs is faster than Atom, because its presentation layer is more efficient (while less capable).

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

#97
post #31

Earlier quoted context omitted.

> Why is OpenGL necessary for a text editor? Why not? Modern desktops are all hardware-accelerated anyway.

Not all graphics hardware is supported by WebKit. For example, Intel 965 chipset doesn't support WebGL.

It looks like Intel hasn't updated the 965 drivers since before Windows 8, seven years ago. The group of people using that chipset is only getting smaller at this point.

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

#98
post #84

Earlier quoted context omitted.

Im probably super out of the loop but I always wonder about these kind of comments. Even if electron uses say 500% more resources than vim, why in the world would that matter beyond personal irritation for anyone making 6 figs doing software development? I get the impression from these arguments that people are trying to do serious software development on 5 year old budget hardware. In any profession, investing in yo…

My gardener once left one of his shovels in my yard for a few hours. During that time, someone stole it. I asked him why someone would steal a shovel, and he said because it was a $150 shovel.

It's always interesting to see how tools of different trades scale. I got into woodworking a while back and discovered Festool. Turns out there is a decent difference between a $200 miter and a $1300 miter. Though much like audio equipment or anything else really there are certainly diminishing returns.

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

#99
post #60

Earlier quoted context omitted.

I have never, even once, in my nearly-20-year career had the desire to collaboratively edit a single, specific text file. Isn't collaboration without conflicts what version control systems are made to do?

I even think it would be annoying if someone would just move cursor around when I edit something. And there definitely would be conflicts if they would try to edit the file at the same time. Who needs this feature?

The way it generally works is that each user has their own cursor.

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

#100

Earlier quoted context omitted.

Can't speak for op of comment, but everyone suggests this... yes I've tried it and no I really don't want it no matter how many times it is mentioned. I am happy with Vim for myself now, and am glad that I moved beyond the bloated IDE way of thinking, including Visual Studio Code. Yes, Atom had its shortcomings in that arena, but I'd still prefer to use Atom over Visual Studio, due mostly in fact that the project has…

Im probably super out of the loop but I always wonder about these kind of comments. Even if electron uses say 500% more resources than vim, why in the world would that matter beyond personal irritation for anyone making 6 figs doing software development? I get the impression from these arguments that people are trying to do serious software development on 5 year old budget hardware. In any profession, investing in yo…

Most laptops top out at 16GB of ram.

Unless you’re only using your editor, you need resources for other things too. VM based dev environments via vagrant, docker etc are very common.

What I don’t understand is why if you’re going to use an editor that’s resource heavy, you wouldn’t just use an IntelliJ product.

Sure, they’re jvm based and “heavy”. But they’re also fucking amazing, and have functionality none of these text editors are ever likely to have. Resource usage is acceptable if there is a benefit to the user.

Oh right. I forgot. You can afford a $3K brand new laptop but you won’t shell out $200 a year for a tool you use basically every work hour of every work day.

Post reply on HN