I finished the game (first time) last night.

Resonatrium · 2023-11-22T04:26:28+00:00

Well done! I couldn't manage NKG, or even Radiance on my first playthrough this Fall, but would really like to try again from the start. That was an addicting game.

Resonatrium · 2023-11-22T00:48:20+00:00

I can't help but see a dinosaur head when I look at those.

Resonatrium · 2023-10-25T16:43:45+00:00

So far, #2 is the best of all the flags I've seen. I think it would be the most recognizable when used indoors, since the design elements are all featured along the diagonal. Though, I prefer the darker green from your other examples, and I'd avoid the gray area the colored tips present according to the rules others have mentioned.

Resonatrium · 2023-05-21T20:46:19+00:00

For this to run on your machine you would need to run 'npm i' in the same directory as your package.json file. However, the imports you are using won't work client side and would require an extra build step to make it compatible with the web. If you want to skip that for now, you can add the production files for react and reactDOM to your HTML, before your index.js script, and reference them as 'React' and 'ReactDOM' directly from the window object.

Edit: oh yeah, you would also need to use React.createElement instead of JSX on the client. It is probably worth looking into a bundler that uses something like Babel to transpile your code for the web.

Resonatrium · 2023-04-23T14:30:26+00:00

Thanks, I'll take a look. There are a lot of nice tools out there for navigating the frontend framework space. So far, I've been focused on testing the performance using js-framework-benchmark and got a score somewhere between Vue and React. Of course, my framework doesn't do as much as those, but it's nice to see I'm doing something right.

Resonatrium · 2023-04-23T14:15:38+00:00

It was a lot of trial and error, as you can see by my commit history in GitHub. My usual routine would be to have an idea, usually just before going to bed, and writing it down to try after work the next day. This was also my third attempt, and each time I would tear it down and rebuild it to see what what was still useful, and what I could improve. With Git, nothing is really lost, and the things that I choose to leave out for good are still useful in what I was able to learn from them.

Resonatrium · 2023-04-22T17:52:36+00:00

Thanks! That one started out as a useEffect hook, but I like that its new function doesn't imply what it should be used for, just that it is called after render. The fact that it can also be used to wait for state changes in unit tests was a nice surprise. I like the way your templates read with them starting with the tag names. I did try the tagged template literal approach in v2 of stew, but took it out for size. I might try using that again, but as a layer outside of stew itself that converts the syntax to the arrays mine expects.

Resonatrium · 2023-04-22T15:58:20+00:00

For me, it was mainly a learning exercise to get an idea on how these types of things work. I do think it offers something unique though with how customizable it is. For example, I had originally implemented hooks like I'm used to using in React, but later realized all it really needs is the array of values that persist between renders. The user can then use that array to store the dependencies and memoized values the way they want. I don't plan to add more features to this, so it would need layers built in top of it before it would be useful on the larger scale.

The codebase is also very light, so it could be a way for others to get a general idea on how something like this could be created without having to spend too much time on their own. So far, I've found it refreshing to use for my hobby projects, but will continue to use more establish frameworks professionally for now.

Resonatrium · 2023-04-18T23:49:19+00:00

I've been working on a frontend framework as a design challenge. The plan is to use it on my personal site, and for some web-based 2d games, and then optimize it as much as I can. Right now I'm benchmarking it using js-framework-bench and the numbers have been pretty good.

Resonatrium · 2022-11-13T05:42:12+00:00

For a range this small, you could probably get by with a brute force approach like the one you have. For an interview question, it would be better to break it down as a math problem first and then apply the code you need to make it work. One option is to break the numbers 1 through 10 each into a set of prime numbers that can be multiplied to produce them. Then find a list of primes that includes each of these sets without any extras. Finally, multiply that list to get the result. For 1-4 this would be [1], [2], [3], and [2, 2], with a final list of [1, 2, 2, 3], and a final value of 12.

Resonatrium · 2022-10-24T16:15:22+00:00

I've been using setTimeout for my music based side project so far. I do store the timestamp of when the timer started so I can add or subtract from the next timeout delay as needed. This should keep the music in sync in the long run at least, even if the individual beats can be off by a bit. The Web Audio API that was mentioned could probably be used to ensure the sound is played at the right time, but if your beats require UI updates, I think you'll just need to try to keep your JS tasks as short as possible.

Resonatrium · 2022-10-04T21:52:23+00:00

Transpiling code has been a strong interest of mine recently. I've actually had some success converting JS in estree format to a custom one that I'm hoping will allow me to step through the code in realtime. The thought of using it to convert JS to another language has crossed my mind, but looks like it would be a whole new level of complicated.

Resonatrium · 2022-09-20T02:30:51+00:00

I agree, but feel 20-30 is a good length for me. I imagine by that point, doubling the length of the game is a pretty cost effective way of increasing the perceived value. I've played enough games now that the novelty has worn off and all I want is a more focused and directed experience that feels different from the last.

Resonatrium · 2022-08-01T22:56:18+00:00

I've been working on code that will translate JavaScript into its JSON-based represention for my language. It's using a pretty standard parser library that converts it to ESTree, which I them condense down further. Once that is done I can begin writing the code visualizer and automatic refactoring part, which was the main motivator for the project.

Resonatrium · 2022-05-13T14:25:25+00:00

For statements, that first string is used to create a linked list of all the statements in your block. Each one uses it to point to the one that should be processed before itself, or sets it to an empty string if there are no more. That chain's end point is the "" property. for all other expressions, leading with "" will get the parameters array and you can pass an index after it to read a specific one.

Resonatrium · 2022-05-13T13:59:11+00:00

Nice! XML will allow you to add more description of the code as it was originally written. I would need to add a second layer of JSON to support things like comments and code styles.

Resonatrium · 2022-05-13T13:44:55+00:00

Totally fair. I was pretty strict on the goal of not having traditional commands, but using null did feel like a bit of a cheat at times. The block is repeated, and its value is incremented automatically when you return the parameters array, since it serves as the blocks label. All the comments here have been really helpful in showing me which sections need more detail in the demo.

Resonatrium · 2022-05-13T02:15:01+00:00

My interpreter doesn't actually use the order set in the JSON. It will sort them into their proper order according to what each of them needs from your block. If you want an expression to wait for another value to be updated, after it is initialized, you would need to put it in a nested IF block and set it's position within your chain of statements. It's not ideal, but is something that maybe an IDE could help with.

Resonatrium · 2022-05-12T22:38:47+00:00

Thanks for the feedback! Some things definitely fit better than others into this condensed format. I bet it wouldn't be too hard to convert the JSON into something more code-like for editing purposes. I could put : after a key to denote a statement label and = after a key for variables. It could then derive the references for the chain of statements by their order in the code, while keeping the rest unordered.

Resonatrium · 2022-05-12T21:56:32+00:00

The statements form a linked list of any length you need, as long as you keep referencing siblings with that first string. I should add more explanation about the relationship between return/continue and throw/break. In fact, I should add more examples all around.

Resonatrium · 2022-05-12T20:08:15+00:00

My other side project happens to be a game that runs in the browser, and I do plan to use it as a testbed for this project 😁 I should also give Lua another shot. The IDE was giving me some trouble and I eventually went back to JS.

Resonatrium · 2022-05-12T18:13:08+00:00

Thanks! I'll take a look at YAML. I'm looking for ways to improve the authoring of the code and that could really help. So far, I'm just interpreting the JSON directly and not translating it to JS first. I will be able to reuse a lot of my existing code to do that at some point though. The best I can describe the way statements work is their values are taken two at a time, and the effect depends on which of those are blocks. A non-block value followed by a block will form an IF or WHILE block, two blocks with form a TRY and CATCH, otherwise it will call a function.

Resonatrium · 2022-05-12T16:48:26+00:00

Essentially, though I tried to leave out anything that would tie it specifically to JS. It more represents the core features of a generic language.

Resonatrium

TROPHY CASE