"for Go and Rust". This is a bit limiting. Any chance to expand to other languages?
Zas Editor
301–310 of 362 posts
Re: Zas Editor
#302Earlier quoted context omitted.
Once you've learn vim keybinds and combinations, nothing comes close for productivity.
Once you've learned vim why do you care if any other editor has vim bindings? What can you do with vim-mode ZasEditor that you couldn't do in vim?
I'm a heavy user of JetBrains IDEs for most of my development work and use it with the excellent IdeaVIM plugin because modal editing is my preferred input method.
I have all the goodies and features of the full IDE with the keybindings and modal editing muscle memory I've built up over the last 15 years.
Technically I can get Vim to do most of what JetBrains does but that's a very very big hill to climb.
Re: Zas Editor
#303Looks like a good start. I need VIM-mode to be able to use it as a daily driver. The ordering of files and directories is a bit chaotic compared to VSCode. I get a "Go is not installed" popup every time I click a .go file which is weird since it's installed and available for the terminal opened in the editor. I would love more language support as well, Elixir would've been awesome.
I'm getting the same "Go is not installed" error. I can't find anywhere in the UI to configure the path to Go - it's most certainly installed.
Re: Zas Editor
#304Hi everyone! I'm the lead developer of Zas Editor. I wanted to share some details about the editor you might be interested in. The text-storage data structure, syntax highlighting and search features are written in Rust, and the UI is written in Swift since we wanted to create a native macOS experience. The Swift and Rust code talk to each other using C FFI, and no, that doesn’t take away the safety features of both…
Congratulations on the launch. There is a demand for a native, fast IDE. I gave Zas a quick spin in our fairly large Go codebase:
Pros:
- really fast
- clean, fresh, minimal UI
Cons:
- Maybe I did something wrong, but one thing I do almost every day is rename something. Right-click a function name (or press F2), pick a better name, done. Zas seems to only rename the occurrences in the current file vs. the declaration.
- The "Open file" suggestions are not great. If I search for a file `moo.go`, one of the first suggestions is `some/folder/moo/some/more/other.go` and then further down the list somewhere it shows `moo.go`
- CMD + click on a symbol should jump to the declaration (or usages)
EDIT: we use GoLand today. Functionality-wise it is great (also builtin TypeScript/JS support is a real plus) but it is slow and hungry.
Re: Zas Editor
#305As a side note, I really like the design of this landing page. Instead of a "hero unit" with a salesy blob text in marketeese, there's a useful description of what the product is, what it does, and what value it adds to the end user, in a way that the user immediately understands.
Each feature description is accompanied by a picture/animation to demonstrate it.
I wish more product marketing pages followed this format, instead of the crappy soulless format of "hero unit" with marketing blob followed by three text boxes in a row with more marketing bullshit.
Re: Zas Editor
#306Hi everyone! I'm the lead developer of Zas Editor. I wanted to share some details about the editor you might be interested in. The text-storage data structure, syntax highlighting and search features are written in Rust, and the UI is written in Swift since we wanted to create a native macOS experience. The Swift and Rust code talk to each other using C FFI, and no, that doesn’t take away the safety features of both…
Mentioning that it’s Mac only, and that it’s not free software, would help keep plenty of people from wasting their time.
I think it is okay to assume that people who frequent a forum mostly inhabited by people who create software for a living would be okay with software that you would have to pay for.
Re: Zas Editor
#307Earlier quoted context omitted.
Mentioning that it’s Mac only, and that it’s not free software, would help keep plenty of people from wasting their time.
I think it is okay to assume that people who frequent a forum mostly inhabited by people who create software for a living would be okay with software that you would have to pay for.
I don't mind that I have to pay for it. I do mind that it's not free software.
Re: Zas Editor
#308Earlier quoted context omitted.
If you want performance, then yes. Shoo! Go back to Electron!
It's still possible to ship cross-platform native software. People just pretend like it doesn't exist because it's too hard, and so I respond by pretending like their software doesn't exist.
I totally understand your perspective, but I'm the opposite. I prefer native apps that utilize the great libraries provided by the OS and function in harmony with the OS (In my case, things like Scrivener, Kaleidoscope, Bear, Things, Alfred, etc.). I only fall back to using cross-platform apps if a native app isn't available, or if the cross-platform app is done really well (e.g., Logseq, VS Code, etc.).
I think it's a good thing that there are people who want to work to satisfy the desires of your niche as well as mine, so we can both be happy and productive.
Re: Zas Editor
#309Earlier quoted context omitted.
It's still possible to ship cross-platform native software. People just pretend like it doesn't exist because it's too hard, and so I respond by pretending like their software doesn't exist.
If it's hard, people are not going to spend their attention on it unless deemed worthy. Like it or not, there is a class of IT-professionals who settled on the idea that macOS won the desktop-game, reasoning that Windows is and will remain trash, and that Linux can't deliver a comparable quality in UX. Someone who wants to focus on building a product can't dedicate the same amount of energy opting for cross-platform,…
Its funny that gaming industry has settled on the idea that Windows won the desktop-game, reasoning that Linux is and will remain trash, and that macOS can't deliver comparable performance.
This is not meant to show that some opinion is better just highlight that people have narrow tunnel vision on what is in front of them and tend to ignore other options without consideration.
Re: Zas Editor
#310There's an interesting potential future here where Apple acquire/acqui-hire the team behind this. As much as I'm keen to see software like this, making an editor work as a business is hard, and Zas has a long road ahead of it. However Apple could really use something like this. Xcode is big and bloated, with a ton of support for features that are no longer the future of Apple's platforms (Storyboards, Objective-C, SV…
Xcode's source editor got a big rewrite in Swift just 4 or 5 years ago. They trumpeted about it at WWDC.