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

Lapce – Fast open-source code editor

lapce.dev

Post reply on HN
Print view View original

221–230 of 231 posts

Re: Lapce – Fast open-source code editor

#221

Post by AllanLRH »

mkeedlinger wrote: post #164
dzhou121 wrote: post #41

Author here. Thanks for all the feedback. I'm aware that Lapce lacks lots of basic stuff. It's a personal project so the initial set of features and key bindings are tight to my personal preferences. I'm currently working on the missing pieces, like multi cursor support(in master but not released yet), mouse support, sane default key bindings(probably I'll stick to an existing editor), basic UX etc. Feel free to subm…

This looks awesome!! The code editor space may seem saturated, but it's not! I've been looking for an alternative to VS Code for some time. Some things I'm really excited for: - Remote development as a first-class citizen! I use code-server a ton now, but getting away from browser jank would be nice. - In the future I wonder if something besides SSH would work for the connection. SSH doesn't handle bad connections or…

I think Microsoft replaced SSH in vscode remote, part of the motivation being that the default SSH port (22?) is often blocked on corporate networks. I believe they use websockets instead, and I wonder if that might help with the problems associated with putting your computer to sleep and resuming your work (and connection)?

Re: Lapce – Fast open-source code editor

#222

Post by tekknik »

mhh__ wrote: post #136
hgomersall wrote: post #37

Earlier quoted context omitted.

Really? I take it to mean "fast and won't randomly segfault".

That should really apply to any systems language other than C for a text editor. As long as you have bounds checking and a test suite you're golden.

Sublime text is written in C, and before VSCode it was arguably the most popular editor on the planet.

Re: Lapce – Fast open-source code editor

#223

Post by tekknik »

dingoegret12 wrote: post #189
ncmncm wrote: post #15

Nowadays when I see "written in Rust" in the title, it reads like special pleading: "It's maybe not as good as what you use, but we are really proud to have got it working at all."

I don't understand this sentiment. Rust is the only language ecosystem where I find that anything works at all. Whenever I have to build something not built in rust, I'm praying. With rust made tooling, I just never have problems.

Have you tried go at all?

Re: Lapce – Fast open-source code editor

#224

Post by tekknik »

playcache wrote: post #101
ncmncm wrote: post #15

Nowadays when I see "written in Rust" in the title, it reads like special pleading: "It's maybe not as good as what you use, but we are really proud to have got it working at all."

I think 'safe'

What makes you think rust is more safe? The platform itself it’s flawed, so any language running on the platform is also flawed.

Load a rust program into mem, change mem, run rust program. You’ve just lost safety.

Re: Lapce – Fast open-source code editor

#226

Post by ho_schi »

mekster wrote: post #191
ho_schi wrote: post #89

No Electron? That is already one good thing ;) Why does Rust folks seem to encapsulate and separate their stuff more and more? Own build-tools and infrastructure are one thing. Am I right that Druid is not an very own Toolkit but a layer like WxWidgets?

Will people stop complaining about Electron once their machine has 8 or more GB of ram?

Actually not. The problem is, good stuff need enduring hard work. There is no justification of wasting resources, draining the battery and providing bad integration into the environment. It is like Flash:

https://josephg.com/blog/electron-is-flash-for-the-desktop/

Why companies use Electron? It saves them money! And the users pay for CPU, RAM and suffer from bad usability. But that doesn't show up on your bill from Microsoft, Zoom, Spotify or Slack. And when your stuck with one software migration to better is hard. Steve Jobs killed Flash for just on reason, battery drain ^^

Re: Lapce – Fast open-source code editor

#227

Post by gigatexal »

marcofiset wrote: post #104
gigatexal wrote: post #98

Supporting modal editing like vim is a huge plus for me. As far as personal projects go this is amazing. Kudos.

It's very barebones though, basic movement + get in and out of insert mode using i/I or a/A. Basic commands like y, d, c + motion are not supported yet.

I know, but given the willingness to throw a bone to the vim community is nice.

Re: Lapce – Fast open-source code editor

#229

Post by still_grokking »

follower wrote: post #209
still_grokking wrote: post #114

Earlier quoted context omitted.

It's funny how people can disagree on pros / cons. For me it's: > - a single binary you can drop in ~/bin Well, a binary larger than quite some operating systems. (And not even talking about the security issues with such an approach). > - native Linux version Well, it's as "native" as an Electron app as it'll execute native machine code at some point. ;-) Besides that it feels as "native" as an Electron app… The UX i…

> Only that Kate is usable right now, and has in fact quite some features. There's dozen of us! :) As a matter of interest, have you managed to get a satisfactory Rust/LSP/Rust-Analyzer/Cargo setup running with your Kate install? (Also, Kate as an AppImage seems to be ~150-185MB as a data point for comparisons. (`libKF5TextEditor.so.5` is ~3.5MB.)) The whole "native UI" aspect is a reasonable discussion point but giv…

> As a matter of interest, have you managed to get a satisfactory Rust/LSP/Rust-Analyzer/Cargo setup running with your Kate install?

Never tried. Like I said, Kate is my "dumb desktop editor". For coding I'm currently using VSC (and have still an IntelliJ install around, in case of).

The AppImage size of Kate is just crazy! Didn't know. That's also not really acceptable. The package version is only 7 MB uncompressed… (And all the libs are shared as I'm using KDE anyway).

Regarding the UX: Maybe I'm just lazy but I'm not keen on learning and remembering different details in how applications work. The "feel" in the 'look & feel' of an app is the most important thing. But as people here mentioned Lapce does not even handle clicks in an "usual" way. A native file dialog is just the tip of the things that should feel "native", imho.

Re: Lapce – Fast open-source code editor

#230

Post by still_grokking »

follower wrote: post #203
still_grokking wrote: post #107

Complaining about bugs in an alpha software makes no sens so I won't. But one thing makes me uncomfortable regardless of its early state: It's gigantic! It's a 55 MB executable. You could fit at least one hundred full blow almost self contained (CLI) text-editors with the feature-set of Lapce in that size… What is going on there? Does it bundle an operating system, or even a whole EMACS distribution in that binary? B…

> It's a 55 MB executable. You could fit at least one hundred full blow almost self contained (CLI) text-editors with the feature-set of Lapce in that size… Sure, why not, I've got time to waste on endless bikeshedding... :D IMO 55MB isn't "gigantic"--a 450MB binary could rightly be called "gigantic": https://github.com/lapce/lapce/issues/24#issuecomment-100122... (But, ya know, ya don't get this here debugging info…

I understand that a code editor is necessarily a little bit bloated.

But my comment was more about the binary size.

I'm very much not a fan of this static compiled apps even I understand that from the developers standpoint they're nice. But properly packaging such a thing is usually more involved as I would be if is would be modular from the get go.

AppImages are a bit better as they're an "overlayed" bundle but still the usual problems remain.

How big would it be if it would use the dynamic libs provided by an distribution actually? I guess not bigger than Kate. :-)

Post reply on HN