Toy VS rust

Over the last couple months or so, I've totally lost my creative spark. I'd been working on a web game and a programming language for 3.5 years and 1 year, respectfully, but both of them reached a point where I don't know what to do next...

Context: I've made my own programming language (Toy), and I'm currently working on a game + engine to go with it. Having some experience with npm, I realize that it might be possible to make something similar to download Toy scripts directly into a mods folder in the game.

Funnily enough, I'm working on a custom scripting language implemented in C. Given how slow Python is, I couldn't implement my lang in it.

People need to promote their langs more - get them out there, you know? Usage is the only way they'll survive.

So I've made my own scripting language called Toy. It was built primarily in a WSL environment, using GCC - the problem is, I also want to support MSVC out of the box. I think it works pretty well as is, with a Visual Studio project provided alongside some makefiles.

And then I wrote the exact same code in JavaScript and C, and compared them. The result was quite good, IMO -

C/C++ is crunchy in a good way, Java is like chewing concrete. JavaScript used to be soft and smooth, but after making my own programming language (which felt silky smooth), JavaScript now feels too soft and sticky.

I'm making a programming language called Toy, which is intended to allow easy modding of video game logic by the players. To this end, each value within Toy, be it a number, a string, a variable name, etc. is stored in a structure called "Toy_Literal".

Don't forget the semicolon.

The goal was partially to make a good jam game, and also to test my custom scripting language Toy. Unfortunately, a combination of a new, crappier computer and the fact that it's an untested lang and engine means that it's really friggin' slow - I'm struggling to get 60fps, even when the simulation rate was adjusted.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.