This page records random ideas that interest me.

Learn about Earley parsing.

Develop a prototype of the code collaboration platform that I discussed in A new home for Timeline.

Host this website on my own server. Re-build website whenever a commit is made. Also keep RLiterate book up to date.

Implement minimal OOP-language in the same fashion as Lua.

Different coordinate systems are suited to different problems. Choosing the right coordinate system makes the problem easier to solve. The same should be true for programming problems. Each problem probably has an ideal programming language in which it can be solved. The task for a programmer should be to find that language, implement it, and solve the problem in that language. Try to find and document examples of this hypothesis.

The ideal language is found if no accidental complexity is present when the problem is solved in that language. That will also make the problem be expressed in few lines of code. So a crude metric of good software is its size. Or rather its size for the functionality it gives.

The goal of a free software community should be to maximize the number of contributors. It is first about community, second about the product.

Explore late bound systems. What does late binding mean?

Explore architecture of B5000 (emulator project). How is it related to Nothing?

Implement the object model in Open Reusable Object Models to understand it better.

Read the book Mindstorms: Children, Computers, And Powerful Ideas.

Read the blog post Computer Revolution.

The STEPS project.

Nice summary blog post: Towards Moore’s Law Software: Part 3 of 3.

Interesting blog: Eli Bendersky’s website (The Expression Problem in Go).

Convert rlselect to an RLiterate document and publish it on this blog.

Convert my dotfiles to an RLiterate document and publish it on this blog.

Write RLMeta blog series:

Site proudly generated by Hakyll.