valadoc-org VS Vale

My favorite thing about Vala personally is the wide range of native libraries you have access to because of its compatibility with GObjects.

There's a great documentation website that has everything located in one place also, which makes development a breeze: https://valadoc.org/

Meson is the preferred build system, and Valadoc.org is invaluable.

You can use guides written for C along with https://valadoc.org.

I'm not sure who needs to be contacted, but valadoc.org is down. I was unable to reach it in Firefox or Chrome. Who do I need to contact? I'm seeing that elementaryOS is hosting valadoc.org, is that still the case?

The official Vala documentation is valadoc.org. I found the ecosystem of libraries around the language yet immature: it's not easy to found information or examples (an often when you found something it's pretty old). There isn't a standardization of the documentation of the libraries. This fact doesn't help a newbie.

I believe Vala is the best choice since the syntax is so simple, and has amazing documentation here

For going further, a lot of the API references are friendlier now. I like Valadoc. PyGObject exists for Python. C and Rust don't seem to have a good centralized source, but the documentation is a lot better now a days.

Vala is not very widely used, but all applications in Elementary OS are written in Vala, and their Developer Docs will help you get started writing your first GTK4 application in Vala really quickly. From there on, you can use the excellent valadoc.org for API reference, or browse the source code of Elementary apps on Github.

I'm often using documentation from another language binding when developing with GTK. Most of the time the Vala documentation https://valadoc.org/, because the language was designed around GLib and GTK. In your case it's even closer, because Vala is a C# knockoff with a different backend. Should keep you clear from C verbosity.

Found a monumental commit 😌: https://github.com/vala-lang/valadoc-org/blob/3f434c8bcd76b711d0262284fadbdeeb47165e6a/README.md

Not to be confused with Vale[0].

[0] https://vale.dev/

The article says they created a deterministic hypervisor that runs all pseudorandom behavior from a starting seed to enable perfect re-playability.

But that's all we know so far. I'm assuming there'll be some sort of fuzz testing, and static analysis or some defining actions that your software can perform.

Honestly it sounds a lot like it has a lot of crossover with what the Vale language is trying to solve: https://vale.dev/, but focused on trying to get existing software to that state instead of creating a new language to make new software already be at that state by default.

Why go through all the trouble when you can do this: https://www.hylo-lang.org/ and not spend a second thinking of lifetimes? No, copies will not be issued unless necessary.

Or why not keep exploring this idea as well? More research-oriented than the first one right now, though, so take it with a grain of salt: https://vale.dev/

Another relevant language might be Vale (https://vale.dev), which is aiming for "perfect replayability": https://verdagon.dev/blog/perfect-replayability-prototyped

Interesting. Very low level though and C(++) centric. She there any thoughts on combining the hardware and OS features with rust or https://vale.dev ?

Use a runtime memory management solution that's cheaper than garbage collection (see Vale)

This seems like a tool I'll be using, and this is an almost meaningless criticism, but why the name?

There's already the Vale programming language (https://vale.dev/), but moreover, I don't get the meaning of "vale". You could call it something like Englint which actually hints its purpose.