111–120 of 231 posts
Earlier quoted context omitted.
At least they went with "lighting-fast" instead of "blazing-fast"
“Lightning fast” is no less meaningless in practice than “blazing fast”. Both get used extensively by projects in such languages as JavaScript and Rust, on projects of similar scope that nonetheless have at least an order or two of magnitude’s performance difference.
It looks really promising. I wonder why code editors have the file explorer on the left side by default, if you resize it you move the whole text (unless you write in a right-to-left language). A colleague made me aware of this a while ago and I cannot stop wondering. I moved it to the right ever since.
2. Edit text.
Flows from left to right.
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…
There are a few factors that contribute more or less to this. In no particular order:
- many dependencies badly handle additional, potentially unwanted features (many aren't optional at all and take runtime checked branches)
- lto is disabled by default on release builds
- release builds still bundle a lot of debug info (should only affects binary, not memory size)
- backtracing on panic pulls in a big backtracing library, formating code and string literals
Enabling lto shaved off 10mb of my build just now
Just tried it, on Linux. Pro: - a single binary you can drop in ~/bin - native Linux version - really, really fast - git branches in the top bar by default Cons (beside being super new and lacking ecosystem): - Use a custom window border, which is also pretty ugly IMO - cannot use arrow keys in the command palette (or any file dialog). I guess it's a bug? - default key bindings are... weird? ctrl+f doesn't prompt a f…
> - 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 is much more important than the actual technology used, imho!
> - really, really fast
I didn't measure anything but at least it feels as fast as my "dumb desktop editor", which is Kate. Only that Kate is usable right now, and has in fact quite some features.
The good parts:
- Lapces packaging issue is solvable.
- Rust is a fast language so I think Lapce won't become too slow as development progresses.
But the no-native UX is an issue. It likely won't ever feel more "native" than any random Electron app; love it or hate it.
But at least I'm looking forward to something like Slint GUI (which hopefully will feel native to my KDE Desktop once it'll be ready).
> You can connect to a remote machine seamlessly, with a "local" experience, benefiting from a identical environment with your production server, or utilizing the full performance of the remote machine. What does this mean? Is it like Emacs' TRAMP[1]? [1] https://www.gnu.org/software/tramp/
It's similar to VSCode's remote development https://code.visualstudio.com/docs/remote/remote-overview Or trying to be.
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…
I thought this is a brilliant output for a personal project. https://lite-xl.com/ is another one which is written in Lua. Brilliant and super fast. It is much more polished than Lapce but still rough around the edges with features though. Another one is Micro which is cool too. Either way I am loving the fact that new OSS text editors coming out.
It looks really promising. I wonder why code editors have the file explorer on the left side by default, if you resize it you move the whole text (unless you write in a right-to-left language). A colleague made me aware of this a while ago and I cannot stop wondering. I moved it to the right ever since.
Honestly, this behavior makes using a vertical monitor almost impossible. Wish VSCode let me configure it like Rider/IntelliJ so the sidebar is just a popover-style drawer rather than a push-style drawer.
Earlier quoted context omitted.
> Windows 7 is EOL and should be treated as such.
True. But it shouldn't be. It's like tearing down a perfectly good neighborhood to make way for a hotel that doesn't really benefit the town.