I defiantly had a far easier time learning c and apply my existing programming knowledge. Getting my head around the borrow checker was one hell of a pain in the ass.
What specifically was difficult to understand about the borrow checker? Much of what the borrow checker requires you to do are things that you still need to do in C just without compiler support.
According to this this slideshow:
At a fundamental level, this is the state of terminal emulators today as I saw it. You have fast terminals, feature rich terminals, and native terminals. You can pick at most two properties to have.
Ghostty aims for – and in my opinion already achieves – all properties.
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).
zellij is a terminal multiplexer like tmux which for example allows you to have multiple terminals shown in the same window. It works both locally and over SSH. Which GUI would do the same?
I’m currently using zellij after previously having used tmux. For me zellij is a direct upgrade in every way, and the default tmux keybindings are even supported out of the box in zellij which makes transitioning incredibly easy. The only downside is that I have no idea how to pronounce the name.
This statement is so categorically ridiculous that I have no choice but to assume that Herb Sutter is deliberately trying to mislead people. I would be very surprised if even 5% of “real-world C++” occurred at compile time. In fact, I would be very surprised if even 5% of “real-world C++” was valid
constexprthat just ran at runtime.