miniblog.

I've never seen a good design philosophy on how to sort compiler errors for the best UX. Do you order by line, or by severity? Do you put the most actionable at the end (because that's most visible when the terminal scrolls) or at the beginning?

Which programming languages follow the "cathedral" design philosophy, where they provide most of: the runtime, stdlib, debugger, LSP, test harness, code formatter and package manager? Go, Dart and Smalltalk are the closest I can think of.

I've built a simple personal wiki/blog at https://notes.wilfred.me.uk/. It has few features and little content, but it works. I've tried to apply an agile philosophy: ship it ASAP. This is hard for side projects. I found the features I wanted after shipping changed considerably!