Toy VS fio

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.

Assuming two systems use flash storage, network bandwidth is identical and it is configured the same way, there should be an issue within the PC, either system or storage drive. Check the system logs for errors and warning events related to data transfer from/to NAS. Try to benchmark the PCs' disks using fio to confirm they have similar performance. https://github.com/axboe/fio

Not specifically addressing your question, but when you get to the point of wanting to start doing some experiments you may find that 'fio' [1] is very handy.

[1] https://github.com/axboe/fio

The dd is not a good benchmarking tool, you should use something like fio and probably tune it to use the ioengine most similar to your use case (eg. a database server will probably use some async IO interface). In your first example (with bs=1G) probably something (the guest OS, the qemu/kvm or the host OS) have split into smaller chunks anyway.

All linux tests are run with fio 3.32 (github) with future commit 03900b0bf8af625bb43b10f0627b3c5947c3ff79 manually applied.

FIO: https://github.com/axboe/fio

Agree, I used flex/yacc to add an arithmetic expression evaluator to fio a few years back to allow simple math with some units in fio's job files, and for stuff like that, they're fine, but I wouldn't want to use them for a real language, the error handling is kind of a nightmare.

Flexible I/O Tester (fio-3.33): https://github.com/axboe/fio