archlinux-installer-script VS neat

I haven't installed it since ~2016/2017, so my knowledge might be outdated. If you use one of the arch-based distros with a GUI, then you're right that it's very easy to install.

If you follow the Wiki though, I think you still learn quite a bit: https://wiki.archlinux.org/title/installation_guide

This is right at the bottom of the installation guide (if you followed it and did not go the install script route). Regardless, it seems that arch is installed, now, either install a desktop environment (Gnome, KDE, XFCE, ... ) or a window manager ( i3, awesome, bspwm, herbstluftwm, ...) -> https://wiki.archlinux.org/title/General_recommendations#Graphical_user_interface.

I'm reading the installation guide. And I'm stick at section 1.2.

I started here https://wiki.archlinux.org/title/installation_guide

Stop following outdated YouTube tutorials and just use the installation guide on the Arch Wiki. All of the information needed is there.

It runs on plain C ABI, so you can just define C functions as `extern(C)`, just as you would in D. But you can also use `std.macro.cimport` to import C headers directly. Check out the Dragon demo, https://github.com/Neat-Lang/neat/blob/master/demos/dragon.n... :

    macro import std.macro.cimport;

Funny sidestory: The way my compiler ( https://github.com/neat-lang/neat ) used to build is, two years ago there was an initial compiler that was written in D. And every time you checked it out on a new system, there was a file with a list of breaking commits, and it would:

- git clone itself in a subfolder

Sure, but keep in mind it's pre-pre-alpha and the current released version is kind of outdated (ping me if you actually want to try it):

https://github.com/neat-lang/neat

This is more a D-like than a C-like, but it only breaks C syntax in areas where IMO C straight up made the wrong call, like the inside-out type syntax.

The thing I'm most proud of is the full-powered macro system, which is really more of a compile-time compiler plugin system.

A good example of a macro would be listcomprehensions: https://github.com/Neat-Lang/neat/blob/master/src/neat/macro...

You can tell it's just compiler code that happens to be loaded at project compiletime.

`compiler.$expr xxx` is itself a macro, that parses an expression `xxx` and returns an expression that creates a syntax tree that, when compiled, is equivalent to having written `xxx`. It's effectively the opposite of `eval`. In that expression, `$identifier` is expanded to a variable reference to "identifier".

So `ASTSymbol test = compiler.$expr $where && $test;` is equivalent to `ASTSymbol test = new ASTBinary("&&", where, test)`. (This shows its worth as expressions become more expansive.)

All in all, this lets you write `bool b = [all a == 5 for a in array]`, and it's exactly equivalent to a plain for loop. You can see the exact for loop at line 103 in that file. `({ })` is stolen from gcc; google "statement expression".