Aside: I detest Discourse. It is an abomination of good ideas mated to horrible UX by developers and designers too caught up in drinking their own koolaid to understand that most people do _not_ live in Discourse and expect the website to act the same way every other website does. Hijacking `ctrl+f` in a webpage should reserve a special spot in hell for the person that decided it was a good idea [0].
[0]: https://meta.discourse.org/t/options-to-disable-hijack-of-cm...
While I agree in general, and likely in this case, I think a distinction can be made based on whether it's more of a webpage, or a webapplication. ctrl-f finding within Google Sheets focuments and applying a background color to matched cells is not something I would want to give up, but that's about as far along the spectrum to application as you can get, so it's fairly cut and dry.
Yes that is a terrible idea.
Also since I experienced nested comments on HN and Reddit I find the old forum format quite a step backwards.
HN is impossible to read when a discussion gets large.
I know that the title is supposed to match the submission, but there are cases where a custom title makes much more sense, and provides a lot more value to the community.
But they do it for a good reason. IIRC Discourse does not load all the contents initially so your conventional Ctrl+F won't work correctly. Mind you, I also hate the hijack, but in this case I decided to bear with the unfortunate reality.
By lazy-loading the rest of the comments, it makes standard browser features like searching and scrolling not work right, yet the bandwidth savings of the initial page load is <2%. You'd have to have a lot of comments on a single page before the cost of simply downloading them all became significant.
Of course, since Swift is a TERRIBLE language, its appropriate they are using it.
