3 ms·

I know that is superficial, but although Rust has many great features it looks too much like C++ for me. All those :: and template<likes> are making it look too

by hawski 8y ago

I know that is superficial, but although Rust has many great features it looks too much like C++ for me. All those :: and template<likes> are making it look too busy for me. Also type inference looks a bit too powerful - it may make things easier to write, but harder to read. Personally I cheer for Zig and think that it has the biggest potential to really become a C replacement for me. Other then that I hope that Myrddin [0] will see stable development till 1.0 and beyond. Myrddin has my vote, because it uses QBE [1] compiler backend instead of LLVM. Now that I think about it it would be cool to see Zig on QBE. I just don't think that the current LLVM monoculture is healthy in a long run. Maybe I'm weird, but I would like to imagine a language like Zig compiled also to DEX for Android and CIL for Windows. Then it could have mostly free platform-native calls. So one could really write truly first-class cross-platform apps. [0] https://myrlang.org/ https://myrlang.org/ [1] https://c9x.me/compile/ https://c9x.me/compile/

AndyKelley 8y ago
> it would be cool to see Zig on QBE. from https://c9x.me/compile/ https://c9x.me/compile/: > Text input only. A C library interface is work in progress. this is a bit of a non-starter > Some ongoing work on the Myrddin compiler aims to use QBE as backend. sounds like myrddin does not use QBE as a backend. ---- It is unlikely that Zig will ever use QBE as a backend, optional or otherwise. However, it is quite possible that in some distant future Zig has its own backend that avoids the LLVM dependency entirely. This would be in pursuit of fast compile times.
- hawski 8y ago
  Oh. You're right. My bad. I thought that they are pretty focused on QBE switch and as Myrddin is still in quite early phase of development I thought it's not much of a difference. Well looking at public commits in main branches it seems that QBE development is not really active. Too bad. I hope that there's a flame remaining. I'm not tracking mailing lists either. It's great to hear that a home grown backend is something even considered for future. I know that it's a long way there, but that's life. Thank you for your efforts with Zig. From all the new systemish languages I find Zig with it's current momentum the most probable to become the C replacement for me.

by hawski 8y ago

AndyKelley 8y ago

> it would be cool to see Zig on QBE. from https://c9x.me/compile/ https://c9x.me/compile/: > Text input only. A C library interface is work in progress. this is a bit of a non-starter > Some ongoing work on the Myrddin compiler aims to use QBE as backend. sounds like myrddin does not use QBE as a backend. ---- It is unlikely that Zig will ever use QBE as a backend, optional or otherwise. However, it is quite possible that in some distant future Zig has its own backend that avoids the LLVM dependency entirely. This would be in pursuit of fast compile times.

hawski 8y ago
Oh. You're right. My bad. I thought that they are pretty focused on QBE switch and as Myrddin is still in quite early phase of development I thought it's not much of a difference. Well looking at public commits in main branches it seems that QBE development is not really active. Too bad. I hope that there's a flame remaining. I'm not tracking mailing lists either. It's great to hear that a home grown backend is something even considered for future. I know that it's a long way there, but that's life. Thank you for your efforts with Zig. From all the new systemish languages I find Zig with it's current momentum the most probable to become the C replacement for me.