Yeah I agree the table is very odd, but the project looks awesome anyway. Some users may care about things using native widgets when it comes to theming and stuff, though I wouldn’t even know what I’d call “native” on Linux. Is GTK native? Qt?

They explain it a bit here: https://mitchellh.com/writing/ghostty-and-useful-zig-patterns

Also, calling out the warning signs, my bar for a native platform experience is that the app feels and acts like a purpose-built native app. I don’t think this bar is unreasonable. For example, I don’t think it’s unreasonable to say that Alacritty is kind of not native because new windows create new processes. Or that Kitty is kind of not native because tabs use a non-native widget. And so on (there are many more examples for each).

So nothing wrong with Kitty on MacOS e.g., but the “feel” is not native. Personally don’t care too much about that, but the author seems to do.

I’ll never get over how cool animated code folding looked when I first saw it. I love my terminal but man that’s sexy. Reminds me of some of the original demos of Dion. I feel there is definitely room to reinvent how we view and edit code.

May not be the most popular choice, but I absolutely love Sublime Merge. Only issue I have is that it doesn’t support workspaces. But I love how it doesn’t abstract git away. Most actions in the UI are just called like the underlying git command, there are no non-git things like a “sync”. Plus you can always click on the top to see which commands exactly were executed and with what output. And it’s Sublime-typical wicked fast.

It’s an unlimited free trial with the dark mode disabled. License costs $100 and lasts for 3 years of updates.

That’s exactly it, no wonder I couldn’t find it. Thank you so much!

yup, my bad. Frankly I thought grapheme meant something else, rather stupid of me. I think I understand the issue now and agree with you.

The way UTF-8 works is fixed though, isn’t it? A new Unicode standard should not change that, so as long as the string is UTF-8 encoded, you can determine the character count without needing to have the latest Unicode standard.

Plus in Rust, you can instead use .chars().count() as Rust’s char type is UTF-8 Unicode encoded, thus strings are as well.

turns out one should read the article before commenting

if your title was “I NEED ANSWERS PEOPLE” then this one’s on you…

This talk is technically not about Zig, but he still shows many of Zig’s strengts: https://youtu.be/aPWFLkHRIAQ?si=b-rf_oM*removed*IvAdq

To me, Zig is a language that tries to be like C, but with all the decades of mistakes removed, or rather with modern knowledge of good language design in mind, while keeping as much compatibility as possible, as to not require a lot of work for the transition as Rust did. Thus, if you’re working in a C codebase, you’ll be good to go to integrate Zig in as little as an hour. They also have by far the cleanest solution to macros and generics that I have seen yet (although I miss my type classes).