seed7 VS zig

This release is available at GitHub and SF. There is also a Seed7 installer for windows, which downloads the newest version from SF. The Seed7 Homepage stays at its usual place. There is also a mirror of the Seed7 Homepage at GitHub.

Seed7 at GitHub

bugmagnet@LAPTOP-H6HBEGA9:~$ git clone https://github.com/ThomasMertes/seed7 Cloning into 'seed7'... remote: Enumerating objects: 21021, done. remote: Counting objects: 100% (4660/4660), done. remote: Compressing objects: 100% (1118/1118), done. remote: Total 21021 (delta 3677), reused 4454 (delta 3515), pack-reused 16361 Receiving objects: 100% (21021/21021), 15.95 MiB | 6.47 MiB/s, done. Resolving deltas: 100% (18593/18593), done. bugmagnet@LAPTOP-H6HBEGA9:~$ cd seed7 bugmagnet@LAPTOP-H6HBEGA9:~/seed7$ make -f src/mk_linux.mak depend make: *** No rule to make target 'chkccomp.c', needed by 'chkccomp'. Stop.

No. You can see at GitHub that I update Seed7 quite often. Approximately once a month I do a release and this release is announced at r/seed7 and here.

The packages are not updated so often. So you are more up-to-date with the releases (or even more up-to-date by pulling from GitHub).

I committed a corresponding change to GitHub (Support syntax statements without $ (dollar)).

This release is available at GitHub and SF. There is also a Seed7 installer for windows, which downloads the newest version from SF. The Seed7 Homepage stays at its usual place. There is also a mirror of the Seed7 Homepage which uses HTTPS.

Yes, I am regularly working on improvements for Seed7. The changes are checked in at GitHub (see here for the list of commits) and once a month I do a release which is announced at r/seed7.

It all depends on the circumstances behind. In the beginning the core-js maintainer had no family and now he has. When I released Seed7 I already had a family. It was clear that my job had to support my family and my hobby (GitHub link).

Syntax highlighting for the Nano editor has been added. Many thanks to Duke Normandin for creating seed7.nanorc.

There is an issue proposing this approach: https://github.com/ziglang/zig/issues/4284

https://github.com/ziglang/zig/issues/224

e.g.:

> > When debugging/prototyping, it's useful to comment out a line without having to refactor, e.g.

When writing code in a scripting language, sometimes you need that extra bit of performance (or maybe an async feature from Zig).

NodeJS is by no means a slow runtime, it wouldn’t be so popular if it was. But compared to Bun, it’s slow. Bun was built from the ground up with speed in mind, using both JavascriptCore and Zig. The Bun team spent an enormous amount of time and energy trying to make Bun fast, including lots of profiling, benchmarking, and optimizations.

ntdll.dll!RtlUserThreadStart()

There are valid reasons to use APIs from NTDLL. Where I disagree with zig#1840 is the idea that it is always better to use NTDLL versions of API. Every other software ecosystem uses the standard Win32 APIs and diverging from that without a good reason seems like a good way to have unexpected behavior. One concrete example is most users and programmers expect Windows to redirect some file system paths when running on WOW64. But this is implemented in Kernel32, not ntdll.

https://github.com/ziglang/zig/issues/11894

Zig also has an IRC channel on libera (#zig) that is moderated by Andrew Kelley.[1]

[1] https://github.com/ziglang/zig/wiki/Community