I ported Purble Place (the kid's game shipped with earlier versions of windows) to the browser using Fable 5.1. It was ported from the exe and it uses the original assets and sounds.
The porting process worked like this:
get resources from the installer using innoextract -> decompile using ghdira -> annotate the decompiled code (there were many debug strings in the code so this was simple) -> analyze and transform the assets -> analyze the decompiled code -> implement the engine and game logic in js
I just added claude code support to ovid (it was originally just a pi extension). It is an extension that makes your coding agent verify the features it builds and record a polished terminal + browser video of each verification onto your PR. The verifications are ordinary code so re-running them is cheap.
link in reply
I added benchmarks, rust style enums (which also enables null safety), a primitive match expression and statement, methods and bound methods. The internal representation of enums was designed in a way that makes it easier to add reflection later.
Claude Fable 5 is great. I was able to quickly make a small statically typed language with a precise gc, aot compilation (using cranelift), generics, lambda functions and type inference. link in reply.
I was only involved in the high level design and implementation decisions.
Claude Fable 5 is great. I was able to quickly make a small statically typed language with a precise gc, aot compilation (using cranelift), generics, lambda functions and type inference. link in reply.
I was only involved in the high level design and implementation decisions.
It doesn't have null safety, modules, control over mutation, string interpolation, inbuilt hashmaps, traits/protocols/interfaces, reflection, ffi, async/green threads, exceptions, methods, enums/unions,etc. but I can make fable add them later.
sharing my ideas too, if you build this i will be your first customer
i am desperate for an 'OpenDevin' but not in the background agent sense, in their autonomous QA sense
the idea here is you give the agent the same tools that you use to develop and use your product, think codex computer use but if it could be turned into e2e tests as well.
you should be able to verify an agents work without having to run anything locally, purely by looking at the e2e test and test output
misc requirements:
- the agent gets real developer tools to test your product (chrome, a terminal, etc)
- the agent is able to develop the app using those tools, and then once it's done developing can turn them into tests in the repo
- you're able to plug in multiple 'targets' to the same / similar tests, i.e "test the dev server, test production"
- be able to run the tests quickly and also against different environments (i.e against MacOS, Windows, Linux)
- needs to be open source and run locally
- needs to output videos that can be played back to see the output
for monetization you can likely turn this into a hosted product with vms to run the tests on but i'm also so desperate for a good version of this that i'd do github sponsors
i've implemented an ok version of this in https://t.co/UfRKF2LkgO but it has so much more potential to be better
if you have built this already, have your agent open a PR to my repo with your product and i'll take a look, if you're interested in building this i will get on a call with you to explain it in more detail
@RhysSullivan Can you take a look and say whether it's similar to what you had in mind?
I feel it's a good idea to talk with potential users before iterating further
@swyx https://t.co/sZgrsvs3sN seems to have something called "App monitoring"
https://t.co/mMSL4elZ4Q. (but I haven't used it so I don't know how good it is)