132 karma · joined March 24, 2010
Ignoring animations and ajax, the core functionality of jQuery orients itself to the concept of progressive enhancement (http://en.wikipedia.org/wiki/Progressive_enhancement), you have a basic functionality of a page in HTML and you enhance that with scripts for better user experience. Hence most of jQuery methods follow the operations required for progressive enhancement: finding DOM stuff and changing it, registering events etc.
This is what in the end conflicts with the design of React. React is (again ignoring server-side-js prerendering) an all-or-nothing approach. The whole dynamic part of the DOM is constructed out of the virtual DOM. There is no no need to find DOM elements, because the React way would just relink your component to the real DOM result of its previous rendering or you find DOM elements of child components via React refs. To follow React design, you only change the real DOM directly if you need to step outside of React to e.g. integrate another library. The normal modus operandi is to just render new new virtual DOM based on your props / state.
You can do some meaningful things with combination of React and jQuery, e.g. just use jQuery's focusin/focusout to make up for the lack of bubbling focus support in React. Mostly though you shouldn't need to -- by design.
Spying on the head of the EU-anti-monopoly investigations against Microsoft and Google is already industrial espionage.
We largely abandoned the enlightenment ideas of a humanist education. One whose purposes it isn't to drill people into fulfilling norms, but that enables them to live fulfilled lives where they can express themselves and grow into the kind of educated citizen being able to judge on political matters beyond who you'd like to drink a beer with more.
So in their infinite wisdom, they replaced it with "Mindestspeicherfristen" / "minimum storage limit" / data retention.
Yes, "poke 53280,0" would directly write address 0xd020 to 0x00 which then e.g. would turn the border black on the C-64. But those were addresses in the mapped custom chips. More like setting a pixel on a modern GFX card by poke and less changing a program.
The later development of expansion cartridges to give you more lives in games or enable a cheat-mode there would a kind of peeking and poking, but hardware based etc.
Note that the code is now only a work-around for older browsers. Every modern browser supports native JSON parsing anyway.
So just going <\/script> is enough.
The validation code they use in case there is no native JSON implementation available is borrowed from Douglas Crockford's json2.js ( https://github.com/douglascrockford/JSON-js/blob/master/json... ) which was the inspiration for the native JSON implementations and should really be correct by now, both in terms of correctness but also circumventing regexp weaknesses in some engines.
I work for as architect for a small consultancy/software-development company and I'm paid the same salary no matter how many hours I actually work. Contract says 40 h/week, but there are weeks when I reach the 40 on wednesday. MIght be able to work less than 40 hours when times are not as stressful (haha), but the average has to be clearly above 40 h/week.