I like to quote the gnu article on pragmatic idealism:
> The GNU GPL is not Mr. Nice Guy. It says no to some of the things that people sometimes want to do. There are users who say that this is a bad thing—that the GPL “excludes” some proprietary software developers who “need to be brought into the free software community.”
But we are not excluding them from our community; they are choosing not to enter. Their decision to make software proprietary is a decision to stay out of our community. Being in our community means joining in cooperation with us; we cannot “bring them into our community” if they don't want to join.
What we can do is offer them an inducement to join. The GNU GPL is designed to make an inducement from our existing software: “If you will make your software free, you can use this code.” Of course, it won't win 'em all, but it wins some of the time.
Proprietary software development does not contribute to our community, but its developers often want handouts from us. Free software users can offer free software developers strokes for the ego—recognition and gratitude—but it can be very tempting when a business tells you, “Just let us put your package in our proprietary program, and your program will be used by many thousands of people!” The temptation can be powerful, but in the long run we are all better off if we resist it.
This may not be relevant, but Zachtronics (a known programming puzzle game dev) nearly always includes zines in the games, and they feel unique and quirky as you say.
If you have ever played Elite Dangerous, you will be unimpressed by this.
The stellar forge (which is a system used to generate the roughly 400 billion star systems which are present in the 1:1 scale Milky Way galaxy in Elite Dangerous) is actually something incredible: https://elite-dangerous.fandom.com/wiki/Stellar_Forge
I'll never get these type of minimalist websites that limit themselves to 80 chars like terminals BUT not center the content. When you have a big display, it's such a pain
The lsp requires you to run "dune build" first, bad already.
If you add a new file, the lsp wont pick it up until you dune build it again.
The compiler errors arent there too.
But i loved writing OCaml, its just thats a bit more painful to learn than due to the tooling, since i didn't use many functional langs before.