Is this a “silly but harmless” or “crazy awesome dangerous” JSON handling, I would like to let you decide. Aeons after the original post, we still have these “JSON is not safe” issues in Chrome 85 and the rest. Few examples: Continue reading
Consider this statement.
|
1 |
fun( alert('Bimbili'), alert('Bumbili') ); |
Besides, reminding us of desperately bad parts of JavaScript (mixed with DOM), what else happens here?
Continue reading
I have just realized there is an “Entity component system” architecture in full swing these days. I very often use gaming development as proof something works or does not work in reality. Continue reading
At the present date and using Chrome version 80. The situation is this:
Well, I could not resist this catchy title, could I? Perhaps I could. In any case I have this idea and implementation where one jQuery plugin is sort-of-a “socket” (not a network socket, but a socket in the wall) into which you can plug-in your “plugs” which will do standard jQuery related stuff. Continue reading
And they are all still very fast indeed.
Originaly posted 30 Mar 2011 Continue reading