I find myself agreeing with the article (although I also agree that it assumes you've chosen an SPA when you shouldn't have). To add my own perspective: I work on an app, the front-end of which essentially consists of 6…
Not to pile on, but I wasn't expecting your "what's this" link to be a magnet link to Discord. Could be worth specifying that, or at least using a pop-out/magnet icon beside it.
A rule of thumb I've been following lately (when communicating in e.g. GH issues or Slack messages), is to use the title of the page where possible. Hopefully, the page title should reflect the page's content, and thus…
I liked your article, but I loved the design of your blog. Very clever use of colours and structuring, and the interactive demo is the icing on the cake. Nice one! (Late reply because I procrastinate reading HN).
At work, I use Vivaldi's tab stacks to group tabs by the GH issue I'm working on. So the issue, PR(s), and app tab(s) go in the same stack. It's very handy.
I find myself agreeing with the article (although I also agree that it assumes you've chosen an SPA when you shouldn't have). To add my own perspective: I work on an app, the front-end of which essentially consists of 6…
Not to pile on, but I wasn't expecting your "what's this" link to be a magnet link to Discord. Could be worth specifying that, or at least using a pop-out/magnet icon beside it.
A rule of thumb I've been following lately (when communicating in e.g. GH issues or Slack messages), is to use the title of the page where possible. Hopefully, the page title should reflect the page's content, and thus…
I liked your article, but I loved the design of your blog. Very clever use of colours and structuring, and the interactive demo is the icing on the cake. Nice one! (Late reply because I procrastinate reading HN).
At work, I use Vivaldi's tab stacks to group tabs by the GH issue I'm working on. So the issue, PR(s), and app tab(s) go in the same stack. It's very handy.