Fabrizio Ferrai

@hdgarrood makes sense. I think at this point then a goal worth pursuing (heh, pun intended) could be to have a single codebase for frontend and backend search, so that...

@JordanMartinez note that this is already done in [docs-search](https://github.com/spacchetti/purescript-docs-search) - what do you refer to when you say "slow down development"?

Reading through this issue again it seems like it's more related to Pursuit itself rather than the Registry, so I'll move it over there and clarify the title

I had a look at the above files, and they look good to me - the list of packages that we'll reserve is minimal and meaningful, and the list of...

Thanks! I think the logistics of that will be tricky over the Christmas days, but I let's see if that works for next week

@thomashoneyman I am through with the review - the overall shape of the code is good, and the only thing left to really resolve is the thing about "testing against...

I think we considered it in the past - the big issue with allowing users to specify compatibility ranges is that they are often incorrect in two ways: 1. overly...

Agreed with Thomas - I'd also like to remark that adding compiler versions retroactively is a "nice-to-have": it's not critical to have this information, so no need to drop packages...

I'm ok with making this a strict check (i.e. dropping packages for which we don't find at least one compiler version), if the amount of post-0.13 packages that we'd drop...

@thomashoneyman agreed - I think "trying to compile a package to figure out if it can be compiled with that compiler version" is a good plan in general, and maybe...