Wait… Neovim also works on windows no?

> without skills

This is not even remotely true

That's his go to for "hello world" for different languages :D. I love it so much.

We all know that OP wasn't asking about THAT kind of interface and more "please create vtables for me" style of interface

That is too much compiler magic for Zig folks.

You know, I used to be annoyed by all your consistently shitty remarks in any zig related HN thread, but these days, it's refreshing to have an unpleasant interaction with a human.

Sincerely, thanks for all your hand-written hatred.

It goes both ways, when I see remarks regarding other languages from Zig community folks, not from you directly.

Modula-2 like safety is still better than C will ever be, though.

Yeah, it will be human as far as I can take it, cheers.

Perhaps it can be a relief to make assessments about a couple of newer C alternative languages[1][2]. Zen C appears to be moving up very quickly, and even has autofree.

[1]: https://github.com/c3lang/c3c (C3)

[2]: https://github.com/zenc-lang/zenc (Zen C)

Sadly no, as fas as I'm aware. I can't think of creating vtables manually every time I need to create interfaces, I guess Zig is not for me.

Yeah I don't understand why a language cannot automate something that routine and boilerplate-y.

Oh well, people like it so I won't judge, I'm happy we have choices for what languages we use. Just wish people would choose safe ones :/

I don’t use zig daily, I rather use Rust, but damn this is awesome. I wish Rust would do this too.

Do what? They do provide a significant number of prebuilt binaries?

Rust relies on a linker being installed (hopefully this will change). There is a lot of Rust libraries that are c wrappers and therefore you will need C compiler installed.

Zig on the other hand ships with everything I need to buy from one host to multiple targets out of the box.

I… didn’t think this makes sense :)

It makes perfect sense: Rust compilers will never beat a human at scheduling every single opcode perfectly based on the deepest microarchitectural analysis short of decapping the chip and breaking out the ol' electron microscope. Whether it's worthwhile to be that efficient over a whole program, as opposed to a preternaturally tight compute kernel, is definitely questionable.

> scheduling every single opcode perfectly based on the deepest microarchitectural

Is that even possible knowing OOE+ branch execution and many other CPU tricks?

Yes it does, that is why most serious games used to be written in Assembly, until BASIC, Pascal, C and C++ compilers got enough language extensions and compiler knobs to not having to do that all the time, and yet some Assembly is still required.

Curious… why not a single app.cs instead of slnx + csproj boilerplate? The moment you `dotnet app.cs` it will be a cached and fast to start

I think the app.cs approach is mainly for single file apps/scripts. While this is small there are two projects and several files so a solution + project files seems totally standard.

Because it offers things where Go today doesn’t and never will?

> the only way to do this incrementally without the massive friction of a full rust rewrite

Any rewrite is massive friction, I’m sure probably meant port? The only annoyance with Rust ports is if you have to support varargs. Hopefully that will come to an end soon.