Re:Show HN: CMS.js – Fully Client-Side JavaScript Site Gener...
by afandian on Tuesday January 19, 2016 @05:12AM
(#10929705)
You should know that your page was blank for about 20 seconds. I nearly closed it.
[ Parent
| on HN ]
Re:Show HN: CMS.js – Fully Client-Side JavaScript Site Gener...
by kecks on Tuesday January 19, 2016 @06:45AM
(#10930056)
Took 6 seconds on a Samsung Galaxy S6, Firefox. I definitely would've closed the tab if I hadn't read this.
Re:Show HN: CMS.js – Fully Client-Side JavaScript Site Gener...
by EvanPlaice on Wednesday January 20, 2016 @03:18AM
(#10936682)
The combined size of the concatenated js/css files was 1.7mb before compression. Now, both combined are 366KB respectively.
The load time should be much better now.
Re:Show HN: CMS.js – Fully Client-Side JavaScript Site Gener...
by plexicle on Tuesday January 19, 2016 @10:30AM
(#10931338)
Oh, it actually worked? I waited a couple seconds and closed it, assuming it was broken.
Re:Show HN: CMS.js – Fully Client-Side JavaScript Site Gener...
by EvanPlaice on Tuesday January 19, 2016 @02:07PM
(#10933062)
Yes, I know. Emphasis on 'working on.' I haven't gotten to optimization yet.
Re:Show HN: CMS.js – Fully Client-Side JavaScript Site Gener...
by EvanPlaice on Wednesday January 20, 2016 @03:13AM
(#10936657)
Try it again.
Re:Show HN: CMS.js – Fully Client-Side JavaScript Site Gener...
by afandian on Friday January 22, 2016 @08:49AM
(#10952633)
5 seconds browser loading. Then blank screen for about 5 seconds. Then a spinner for about 3 seconds.
No matter how much optimisation you're doing, you're still destroying the progressive loading of HTML pages and the ability for my browser to tell me how my page is loading.
It may be a fun project, but it's not based on sound technical decisions, in my humble opinion.