4 ms·
I see that to use Brighton you need to import a bryton.js file and call "bryton()" on the onload event of the <body> element, and this rings my bell: isn't this
by knocte 11y ago
I see that to use Brighton you need to import a bryton.js file and call "bryton()" on the onload event of the <body> element, and this rings my bell: isn't this a downside compared to normal javascript code?
Non-trivial web pages will take a bit to download fully and load, and sometimes you need your javascript code to act as quickly as it can (that's why very often the js <script> tags are all over the place in the HTML code, not just at the beginning and activated by the onload event).
- dtech 11y agoIt's the downside of every non-JS client browser language, you currently either have to compile or interpret it.
- knocte 11y agoWell, the Python-to-JS conversion could happen in the server and then this problem would not be there (but then there would be no Python when viewing the source of the page, I know... which is... less fancy?).
- pekk 11y agoYes, Javascript will still be the fastest option with the cleanest support. That's because browser vendors have intentionally put everything else at a disadvantage (Mozilla ensuring nobody puts Brendan Eich's baby in a corner). The most anyone can really do is generate slight variations on the spelling of Javascript, which has other big disadvantages. All of this is a downside compared to normal programming.
- woah 11y agoIt's all a huge conspiracy
- deleted 11y ago[deleted]