The old title was "Official Swift forums switch to Discourse," or something along those lines. The current title ("Swift Forums") tells you nothing . 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 we…
meta: I noticed titles getting changed to something nonsensical more and more often on Hacker News. The current title is absolutely ridiculous, as it provides no value. 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.
Swift Forums
11–20 of 23 posts
Re: Swift Forums
#12Earlier quoted context omitted.
Looks like discourse [0] to me which is an open source ruby forum software 0: https://github.com/discourse/discourse
Damn, I was hoping they dog-fooded some server-side swift. I was just interested in seeing a larger server-side swift project not the actual forums themselves. Thank you for the link, though.
Building a large exploratory project in Swift and having a robust place to have technical conversations should be two different projects.
Re: Swift Forums
#13The old title was "Official Swift forums switch to Discourse," or something along those lines. The current title ("Swift Forums") tells you nothing . 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 we…
Ok what do you like then? PHPBB (or similar)? A mailing list? A FB group? BBS?
Re: Swift Forums
#14Re: Swift Forums
#15The old title was "Official Swift forums switch to Discourse," or something along those lines. The current title ("Swift Forums") tells you nothing . 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 we…
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.
Re: Swift Forums
#16The old title was "Official Swift forums switch to Discourse," or something along those lines. The current title ("Swift Forums") tells you nothing . 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 we…
Ok what do you like then? PHPBB (or similar)? A mailing list? A FB group? BBS?
Re: Swift Forums
#17The old title was "Official Swift forums switch to Discourse," or something along those lines. The current title ("Swift Forums") tells you nothing . 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 we…
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.
Re: Swift Forums
#18Re: Swift Forums
#19Re: Swift Forums
#20The old title was "Official Swift forums switch to Discourse," or something along those lines. The current title ("Swift Forums") tells you nothing . 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 we…
> Hijacking `ctrl+f` in a webpage should reserve a special spot in hell for the person that decided it was a good idea 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.