Show HN: Brolly, a plain-text weather forecast site
11–20 of 91 posts
Re: Show HN: Brolly, a plain-text weather forecast site
#12Looks great. One thing that initially tripped me up, I searched "Raleigh, NC" and got no place found. "Raleigh" worked.
Re: Show HN: Brolly, a plain-text weather forecast site
#13Re: Show HN: Brolly, a plain-text weather forecast site
#14Re: Show HN: Brolly, a plain-text weather forecast site
#15would be great to show humidity %
Re: Show HN: Brolly, a plain-text weather forecast site
#16Re: Show HN: Brolly, a plain-text weather forecast site
#17I love plain text services. One of their benefits is near instant load time. A nitpick, but this takes a few seconds to load on a fast broadband connection for me. I get the delay even refreshing the same page, where I'd expect the cache to be hit.
Re: Show HN: Brolly, a plain-text weather forecast site
#18I love plain text services. One of their benefits is near instant load time. A nitpick, but this takes a few seconds to load on a fast broadband connection for me. I get the delay even refreshing the same page, where I'd expect the cache to be hit.
I’ll take a look though at whether there’s anything causing fundamental slowness in the cache read / page rendering pipeline.
Re: Show HN: Brolly, a plain-text weather forecast site
#19I love plain text services. One of their benefits is near instant load time. A nitpick, but this takes a few seconds to load on a fast broadband connection for me. I get the delay even refreshing the same page, where I'd expect the cache to be hit.
Sorry about this, and thank you for the heads up. The site runs as a PocketBase instance on a small 512mb DigitalOcean droplet in their London DC, and is getting more load than usual at the moment. I’ll take a look though at whether there’s anything causing fundamental slowness in the cache read / page rendering pipeline.
Re: Show HN: Brolly, a plain-text weather forecast site
#20Earlier quoted context omitted.
Sorry about this, and thank you for the heads up. The site runs as a PocketBase instance on a small 512mb DigitalOcean droplet in their London DC, and is getting more load than usual at the moment. I’ll take a look though at whether there’s anything causing fundamental slowness in the cache read / page rendering pipeline.
Looking at chrome dev tools, it looks like it might be the custom font causing the delay. I'm not sure exactly why though.