Alex

I like the idea of pushing a commit to `release` called `v1.0.0` or whatever for updates. Or commiting changes to a file `VERSION` with the current version number and it...

Just realised something - `~/.gravity/satellites` can probably contain every package that has ever been installed if each is versioned, and symlinks can be used for caching and stuff. That'd be...

```ruby import "test" # module named test. See issue #37 import "test.gravity" import "test.so" import "test.dll" import "./test" # looks for test.gravity, then test.dll, then test.so? ```

@cartman300 yep, that's what I was getting at with `import "./test"`.

> we should also need a file extension for json bytecode Neko's bytecode is `.n` - we could use `.g` for Gravity bytecode?

I'd say use WebkitGtk or QtWebkit where possible, and use Chromium if they don't exist on the target distro - i.e. compile separately for different Linux distros. Assuming gtk/qt aren't...

~~I'm pretty sure I fixed that bug a while back @MonsterDruide1~~

We can fix this by writing this hook ourselves to keep eating repeated calls and only send out the request after n ms has passed. Perhaps `{ leading: true, trailing:...

i.e., a 'source code' option when creating a new scratch that is used instead of the C code given by mips-to-c, if provided

Backend already supports this