It is widely known that every corporate developer has endless time for his work. Mundane aspects like costs of development should have no impact on our code, the pureness of which is a goal in itself.
> It's called "Vernichtungslager" / "Concentration Camps", their whole purpose is the legal killing of undesirables, you're really venting your anger at the wrong agency here. They're just doing the job they were hired for.
Something tells me there will be no meeting 50 years after the torture in US secret prisons -- especially none with any insight into the wrongness of it.
It's not really a bug for the same reasons that jQuery implements focus/blur independently from focusin/focusout. focus events just don't bubble out natively so you have to make your synthetic event system do that if you want / need it. jQuery implements it as a separate pair of events, React chose not to / only deviates from DOM behavior in very few instances (onchange). Using jQuery was just easier for my use case which seemed too exotic to claim any kind of general relevance.
There's quite a functional overlap between many uses of jQuery and what React does.
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.
I think it's deluded to expect any country to come even close to what the US is doing except maybe China. The budgets of all are not anywhere high enough to pull such a thing off. The US has moved on a dark and lonely path after 9/11.. Not only in espionage, but also in remote killings, illegal imprisonment and torture. To say others do just the same seems deluded.
I think the main problem is that these days we tend to look at this as a purely quantitative matter, when it's largely a quality matter.
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 it would kind of be more meaningful to not compare to the national average but to private schools targeting the same socio-economic situations, but with a traditional curriculum.
Not really. They have been supporters for "Vorratsdatenspeicherung" / "stock data saving" / data retention for quite some time and now realize that the populace is not amused by the NSA shenanigans.
So in their infinite wisdom, they replaced it with "Mindestspeicherfristen" / "minimum storage limit" / data retention.
Child abuse is not happening on the internet or mobile phone though, but usually at home. No internet surveillance is going to change any of it. You'd have to start installing cameras in every child's living rooms.
Were there ever really common peek and pokes that would change programs?
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.
Ironically, just like for the American plea bargaining, the risk of the German system is hardest for those actually innocent. The differential between falsely confessing and not might not be as much as in the American system, but in the end it has the same effect. The innocent face even longer imprisonment if they insist on their innocence, in Germany it just works over the rehabilitation angle. The prison system will judge the refusal to show remorse and not trying to make amends as sign of lack of rehabilitation which will lead to a full imprisonment without early release, as opposed to the guilty case who is probable to get out after I think 60% of his time.
If you can find a case in which the validator fails, it's wrong. Otherwise, if it's looks like a JSON parser and works like a JSON parser, i.e. is indistinguishable from a "proper" parser, it makes no sense but satisfying OCD to rework it.
Note that the code is now only a work-around for older browsers. Every modern browser supports native JSON parsing anyway.