Thx K-Sato, we're painfully aware of it. We wanted something we had 100% perfectly control over, that was super "rich", allowing us to easily create "complex code", so we chose Angular, thinking "SSR would solve everything for us". However, as we started turning on SSR, we found several problems. One of these being performance, since the site becomes very large. Another being caching, which seems to be way too aggressive, making it almost impossible to have users see different content than whatever they saw at the site the first time. But we'll probably figure both of these issues out as we proceed. The site is very new and was just published a couple of days ago, and we're constantly improving on it :)
The site is slow, and we're working on it, and we'll probably be able to optimise it at least much more than the speed it's currently having ...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thx K-Sato, we're painfully aware of it. We wanted something we had 100% perfectly control over, that was super "rich", allowing us to easily create "complex code", so we chose Angular, thinking "SSR would solve everything for us". However, as we started turning on SSR, we found several problems. One of these being performance, since the site becomes very large. Another being caching, which seems to be way too aggressive, making it almost impossible to have users see different content than whatever they saw at the site the first time. But we'll probably figure both of these issues out as we proceed. The site is very new and was just published a couple of days ago, and we're constantly improving on it :)
The site is slow, and we're working on it, and we'll probably be able to optimise it at least much more than the speed it's currently having ...