Comments by "" (@pierreollivier1) on "Brodie Robertson" channel.

  1. C++ ? come on let's be serious
    5
  2.  @Or1g3nn  Yes it's GTK without the GTK backend it's instant, same on MacOS
    3
  3.  @acpp23  C++ has too many problems, it's basically a worst C from a C perspective, 99% of the features are useless, the tooling is as bad if not worst, the compilation time on it's own is a no go, and it carries the same broken semantic as C. I really don't see what they would get, just less control, more implicit stuff, and worst compilation speed, all of that for nothing. There is a reason why nothing in actual low level. Even MS is replacing C++.
    2
  4. I think there are cool features, I don't think it's anything ground breaking or earth shattering, but it's basically the best standard compliant implementation of a terminal i've seen, I live in the terminal and didn't have to do forensic analysis into github issues and stack overflow to understand why a keybind didn't work as expect in a TUI application. It's fast like most terminal these days but still, it's fairly plug and play, sane defaults, very easy to build from source. I mean is it worth switching over ? probably not, is it good ? yes definitely. I also really love that they have all the iterm2 themes out of the box. Took me 5 minutes to tweak and I was good to go.
    2
  5. I don't think it's anything ground breaking, but I've used it for the last couple months, and I think I will stick to it. Easy to build, fast, very spec compliant, builtin iterm2 themes. Nothing crazy but I like it. I'm also excited about it's future.
    1
  6.  @mmstick  The problem with C is not one of memory safety, that's a consequence not a cause. Zig tries to fix the cause, which ends up resolving 90% of the consequences at 10% of the cost of something like Rust. Like the linux kernel is 17M loc of pure C, it's crafted by the most talented devs in the world, and honestly with such a wobbly and error prone language is actually incredible how safe and well made the kernel is. So if anyone (because I don't really care if Zig ends up wining) can offer a language that has similar semantic but modernized C semantic, sane defaults, actually helpful compiler and really well made and useful tooling for debugging and crafting high quality code, than It's not even a question of if it will win against Rust, it just will. Yes Rust does make writing safe and correct code somewhat easy, but nothing comes free, and I'm not sure the community of the linux kernel as a whole is willing to pay the price that comes with Rust. But full disclosure I have zero ball in this game I really don't care which languages ends up landing in the kernel, and I would be happy if it's Rust, I just think it's a hard sell.
    1
  7.  @doublescoopovanilla5835  There are even dumber reasons, but sometimes you cat the wrong file, and if your terminal sucks, you basically have to ctrl+d and restart a new one. There are other examples but slow terminals are actually noticeable if you area using the terminal.
    1
  8.  @Kapendev  Emphasis on the "should" but the reality is that they don't Ghostty as well as most recent terminals written in fast languages are fast and it's noticeable
    1
  9.  @Kapendev  That's different, when you make anything in Python you are basically making a game in C/C++. If you were to make a game entirely in Python, your game would be a slideshow.
    1
  10.  @kuhluhOG  Completely agree, I understand why Rust encodes lifetimes in the type system because those annotations are needed for the lifetime analysis, but at the same time. Lifetime are not a set in stone thing, this is why I find that languages like Zig is in this case imo superior because lifetime is managed by your allocator. So I can have let's say a linked list, and Idk maybe I can allocate my node with a fast static allocator on the stack because I know those nodes need to live only for that function, maybe I want those nodes to live for a frame time, so I might use an arena, or maybe I just need to allocates a few nodes here and there in which case a heap allocator is ok, but now I want to debug something so I can swap that with a debug allocator and a logging allocator to track my allocations. The point being that I think Rust would benefit from an actual allocator interface, that could offer to the compiler some lifetime guarantees, because structs should have generic lifetime in 99% of the cases and should be managed by the developer locally, I think this would help reduce the syntax clutter and also make the code more explicit and self documented
    1