The philosophy of all current and future Aelve’s projects is that everything is always considered our fault and then we just figure out what to fix first
In Chrome and Firefox they are somewhere in the preferences, in Vivaldi I had to dig into the flags page
The section "Guides and tutorials" is that also meant for tutorials to various topics?
I’m not sure, to be honest. Mixing content and links in one section might not be the best idea. Perhaps the “Guides and tutorials” section should be renamed to something like “Original guides and tutorials”, and all other stuff should be linked from respective items
Thoughts on using a lighter blue for unvisited links and darker for visited links?
https://imgur.com/a/hBitPrz
https://imgur.com/a/hBitPrz
Then you still get the visual cue for what you've visited before but its not distracting from the content
Perhaps let’s steal the exact shades that people are used to, e.g. from https://stackoverflow.com/ (they are similar there but more subtle, I think)
Just added a section on
do notation, it still needs a lot of work but one thing I remember being hard when I was learning was a concise explanation of how do notation works with examples. See https://guide.aelve.com/haskell/do-notation-eg3jkvay
I really like your explanation of
do! However, if you are aiming at beginners, it might be sensible to use more parenthesis instead of $.
I'm also a little loose with language in a few spots, like "Read a line of input from the console, the string that is read is returned", while not wrong it isn't exactly correct either since it doesn't return a string, but I couldn't think of better beginner friendly wording. Any suggestions?
Also, what's the status of authentication so that changes can be tracked/attributed. I imagine this would be a good way to audit any spam changes that get made instead of the changes being made anonymously.
I expect that the new frontend will become the default in less than a month.
Your PRs for the old frontend will all be merged in and they’ll make the old frontend more pleasant to use for this month, but you might also want to look at the new frontend:
cd front
npm install
npm run start:dev
The new frontend currently pulls the content from staging (for convenience), which runs at http://aelve.com:4801. We reset it to production content every now and then :)
Staging will soon be updated to serve the new frontend, I just haven’t gotten around to that.
(By the way: if anybody wants to get their hands dirty and help me with deployment, I’ll gladly add your key to the server.)
After reading https://www.reddit.com/r/haskell/comments/9t7jmp/haskell_worse_than_go_ocaml_yes_this_is_a/ it looks like there's a number of places we could improve docs, especially around best practices and optimizations
And this is a problem that I’m not yet sure how to solve
Pull requests against libraries, that's what I did with http://hackage.haskell.org/package/containers and it worked really well :)
(The same principle can probably be applied to other things)