201
top 50 comments
sorted by: hot top controversial new old
[-] uid0gid0@lemmy.world 107 points 9 months ago* (last edited 9 months ago)

runs only on MacOS

And

get it into the hands of millions of developers

Seems contradictory

[-] expr@programming.dev 28 points 9 months ago

Yup. Especially since it's written in Rust... Like why? Rust has a great cross-platform story.

[-] priapus@sh.itjust.works 12 points 9 months ago* (last edited 9 months ago)

they've written a custom GPU framework to achieve the performance the level of performance they have. it's currently only compatible with macos, but is being ported to other operating systems.

[-] Blackmist@feddit.uk 13 points 9 months ago

How much GPU performance do you need for text?

[-] expr@programming.dev 5 points 8 months ago

For sure. If 32-year-old vim can handle multi-GB files smoothly, you don't need a GPU.

[-] AnUnusualRelic@lemmy.world 3 points 8 months ago

I remember when we ran text editors on a turnip. It wasn't much but we were happy.

[-] SorteKanin@feddit.dk 6 points 9 months ago

Why in the world wouldn't you just use Vulkan? Then it would still be portable to other platforms with probably still good performance, no?

load more comments (5 replies)
[-] priapus@sh.itjust.works 10 points 9 months ago* (last edited 9 months ago)

runs only on MacOS for now

it will be released on both Linux and Windows, with Linux support currently being the top ranking issue on their GitHub page. they have a tracking issue showing that many pr's have already been merged working towards Linux support.

load more comments (1 replies)
[-] dditty@lemm.ee 48 points 9 months ago

Sounds cool! Too bad it's only on MacOS atm

[-] rimu@piefed.social 48 points 9 months ago

They wrote their own GUI toolkit (oof) and it's hardware accelerated (argh), so OS portability is going to be unusually difficult unless they planned for it from the beginning. No mention of that in the article, so I doubt they did.

[-] hypertown@lemmy.world 23 points 9 months ago

They already have very experimental Linux support. You have to build whole app yourself though. I'd say that in month or two we'll get a binary. You can track Linux porting progress in this issue

[-] heyoni@lemm.ee 3 points 9 months ago

Anybody got a nix flake though?

[-] Carighan@lemmy.world 16 points 9 months ago

I mean on the one hand, the hardware acceleration is awesome. The GUI toolkit is not of course (I assume MacOS has a default one to make everything look like it belongs?), but at least they made it look like a native app instead of the usual electron shit where it's clearly a web page with a window border and some design 15y old me might think is cool but 16y old me would already have been ashamed of.

load more comments (1 replies)
[-] saddlebag@lemmy.world 7 points 9 months ago* (last edited 9 months ago)

Its already possible to build manually on linux and there's a tracking issue.

*edit. same as the other post

[-] ryannathans@aussie.zone 5 points 9 months ago

Sounds like gimp with gtk (gimp toolkit) all over again

[-] LinearArray@programming.dev 13 points 9 months ago

I'm waiting for it to come on Linux.

load more comments (3 replies)
[-] parens@programming.dev 30 points 9 months ago

Looking forward to the memes once this dies

(Zed's dead)

[-] Sanctus@lemmy.world 20 points 9 months ago* (last edited 9 months ago)

I'll be watching this one. It looks nice. Please come to Linux. I do loves me my vim. I did not like setting it up as much as I thought I would to be an IDE. I'm sorry I was mean Zed.

[-] Azzk1kr@feddit.nl 10 points 9 months ago

I've been trying out Helix as of late. It's a bit different than vim, but I'm beginning to like it.

load more comments (5 replies)
[-] NeoNachtwaechter@lemmy.world 4 points 9 months ago

Yes, that was mean, because nobody is able to make another editor as powerful as vim.

[-] nflamel@lemmy.world 8 points 9 months ago

Time will tell for sure, but helix is looking really good and once they have support for plugins I'm rather sure it will be a very, very powerful editor.

I don't think helix will ever catch up to a lot of vims lesser know features of which there are a lot. I think that's by design as well, I think that helix wants to have a smaller surface area than vim and for a lot of people that will be the right choice. I personaly use ex-commands for example, or the quickfixlist fairly often so for me I have a hard time imagining helix not feeling like a step down power-wise (as nice as multiple cursors are).

[-] abhibeckert@lemmy.world 2 points 9 months ago* (last edited 9 months ago)

VSCode has way more features than Vim. Including the ability to run Vim inside the IDE. Or Emacs.

[-] balp@lemmy.world 3 points 9 months ago

Sais no-one that knows vim, thou it have a vi-like mode that is missing most advanced vi-trixs.

[-] priapus@sh.itjust.works 2 points 9 months ago

I was also disappointed not to have ex-commands, but I soon realized Helix's use of multiple cursors with commands that support regex can accomplish the same tasks in a way I found more intuitive. Definitely took a bit to get rid of my :%s/new/old/g muscle memory, but Helix's select command works very similarly and just as quickly.

Quickfix commands on the other hand I never used. It seems Helix has some features such as jumping to diagnostics and errors, but it doesn't have the ability to do so automatically after running make like Vim does (afaik). I don't write much C, so I didn't know that feature existed to begin with.

load more comments (2 replies)
[-] tunetardis@lemmy.ca 15 points 9 months ago

I tried it briefly. It certainly is a lot snappier than Atom ever was, I'll give it that. Seemed to be pretty good with Python, but when I opened some C++ source, it went around reformatting my indentation and replaces tabs with spaces. I will have to see if there is a way to disable all that, as I found it obnoxious.

[-] QuadriLiteral@programming.dev 8 points 9 months ago

If I wrote an IDE and detected tabs I'd just have it delete the codebase

[-] tunetardis@lemmy.ca 7 points 9 months ago

It was more than just tab conversion. For example, it decided on its own that:

if(...) {
    ...
}
else {
    ...
}

would look better like:

if(...) {
    ...
} else {
    ...
}

I mean I guess I could live with that, but really? I imagine there's some config where you can disable all this, but it just doesn't seem worth some giant git commit every time I touch a file with the editor.

[-] tunetardis@lemmy.ca 6 points 9 months ago

Ah I think I found it. I need to go:

{
    "format_on_save": "off"
}
[-] Flipper@feddit.de 3 points 9 months ago

My guess is that it has that default because they use Rust. Everyone uses rustfmt so everything looks the same and if you always format before a commit you never get massive diffs.

Most rust projects I've seen even have a ci job to check the formatting with rustfmt.

load more comments (1 replies)
[-] Pika@sh.itjust.works 11 points 9 months ago* (last edited 9 months ago)

Honestly even if they had coded this to anything other than MacOS I wouldn't use it, I'm not too keen on learning a software that's developed by a team that archived their previous project, given how popular atom was when they decided to archive it it concerns they could just do the same with this one.

[-] Daeraxa@lemmy.ml 10 points 9 months ago

On the plus side, the fact they stopped Atom development has allowed our community fork of Pulsar to flourish and it has seen loads of active development over the last year. I do find it hard to blame the original team, it was clearly a Microsoft thing to make sure they put all focus on VSCode.

[-] zehcnas34@programming.dev 7 points 9 months ago

I’m assuming it was a MS decision

[-] milicent_bystandr@lemm.ee 10 points 9 months ago

Shout out for Lapce.

I remember reading a bit about this (from Atom) a while back and having iffy feelings... I don't wish to slander based on vague memories but certainly at the time I hoped Lapce would catch on instead.

It's still in development, but has a handful of aspects that I really like as the right way to go about things.

https://lapce.dev/

[-] cozy_agent@lemmy.world 9 points 9 months ago

Nice, been finding vscode more and more laggy after each update, so hopefully this is something to replace it with at some point.

[-] FooBarrington@lemmy.world 6 points 9 months ago

The inevitable cycle of modern open-source text editors. First there was Atom, then that got too slow and most switched to VS Code. Next seems to be Zed... I wonder what comes after it!

[-] DrDeadCrash@programming.dev 4 points 9 months ago

Lapce looks pretty cool, for an alpha.

load more comments (1 replies)
load more comments (1 replies)
load more comments
view more: next ›
this post was submitted on 27 Feb 2024
201 points (95.9% liked)

Programming

17314 readers
52 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS