It is just because since all the JSFiddles are on one page. All the console.log would be together in the console and it would be difficult to know which console is for which code.
Hence document.write is used.
Though HTML could be used but that would just increase one more tab to show useless HTML. ;)
You can use them to call some functions when an object property is called or set. P.S. Just like Database triggers ;).
You can use them conditionally to manipulate data before fetch or before storing.
For example: you want to store the username when a person registers using the email id like [email protected] then you can use it to generate username from it by truncating the later part and generate unique username which will be "userzyx" here.
Just open up your brains and see where further it can be used and possibilities are just unlimited.
I especially liked the "construct" part as we can use it to take input from the users in frontend as a numbered value and then store it in the database with the currency format which can be later used to make the value visible with the currency in the frontend.
At that time it was on a slow server with multiple sites loaded on that server.
You can check the speeds now.
If still you have complaints regarding speed kindly comment or raise an issue over there.
By the way the issue was with the server and not the boilerplate.
Currently the site is down due to heavy traffic. The docs are written and in progress. You can also view pages on github wiki. Thank you for checking it out. :)
It is not a static website. It is made using the same boilerplate that is mentioned in the documentation. As the repo maintainer believes in using what he has made. ;)
No it is based on es6/7 jsx. Also it has server side rendering, code splitting and many more features. Kindly check the github repo link shared by tirthbodawala.