docs: Update roadmap

[max-sixty]

This is now ready for review. I'm happy to discuss things here. It's also fine if we merge without complete agreement and discuss on the next dev call.

[max-sixty]

Rendered:

[aljazerzen]

I've pushed two commits to roadmap branch - i don't have access to this one.

There is still quite a few things to do in language design, but I think it'll be fastest to discuss that on the call.

[max-sixty]

I've pushed two commits to roadmap branch - i don't have access to this one.

Hmmm, this is ticked, so I would have thought you had access...

I've pulled it in though

(as you can see I've started using a fork rather than the main repo the past few weeks)

[aljazerzen]

Oh, I didn't know I had write permissions, it does work.

(as you can see I've started using a fork rather than the main repo the past few weeks)

Why though?

[max-sixty]

Why though?

There was no downside to using a fork + I didn't want to be "special" just because I had been using the main repo when it was under @max-sixty in early 2022.

And I wanted to ensure I wasn't missing anything with the contributor experience; e.g. I only recently realized that folks were getting failures on GitHub Pages deploys on their own fork (I fixed that by turning it off in forks)

If you prefer using the main repo, totally fine ofc!