IRLIamOffline

Went from a Gaggia to a Flair and can only recommend it. For me, the Flair only falls short when you want to make >2 espressos at a time. Love the control over every parameter and that you don't need to preheat for 15 mins

I agree that defining a goal along with metrics would be very helpful to make meaningful progress towards AGI. However, defining this test is extremely hard, to a point where I'm not sure if we could define a test like this. So far it seems, that just by defining a test we can come up with a narrow AI that optimizes for this test.

It's interesting that you bring this up, because I'd consider Go and Haskell as almost polar opposites. Go is a simple language which lacks expressibility but with strong opinions on almost everything from formatting to architecture, which leads to a streamlined (and refreshing) developer experience.

Haskell is a complex language, with an expressive type system giving you more tools and guarantees but I would call the learning / dev experience everything but streamlined.

I wonder whether the difference in the organisational structure (single entity vs community) manifests in the characteristics of these languages.

The post makes it sound as if Go being Google's language (not the community's) is a bad thing. I don't see where this sentiment is coming from as the strong opinions enforced by Go core devs is probably one of the defining features of Go.

As with many open source projects under benevolent dictatorship, this can result in streamlined and consistent features with long-term success.

Looks really good already. Think there actually is potential to target people for who Google Docs is too overloaded. Like the idea of supporting markdown.

It might also be really useful to support syntax highlighting as I see one use-case for really quick and uncomplicated pair programming.