mcav

From that article:

> Blinded clinical trials show that people with MCS react as often and as strongly to placebos as they do to chemical stimuli; the existence and severity of symptoms is seemingly related to perception that a chemical stimulus is present.

Windows XP was released in 2001.

> The intent of React is to drive new developers away from the building blocks of the web.

That’s not React’s intent.

That's brain-chemistry-related, with psychedelics competing with the SSRI for your serotonin receptors.

Building a powerful sandbox that maintains anonymity is a difficult problem. The statement that CSS is overpowered is clickbait for a different argument.

Your criticism might be better understood with less prejudice; perhaps something like this instead:

"Websites should not unnecessarily require JavaScript."

Quantity of smoke inhaled is several orders of magnitude smaller than with cigarettes. There's some evidence to suggest that, whether due to quantity or other factors, smoking marijuana casually does not substantially harm lung function[1].

[1]: https://www.scientificamerican.com/article/casual-marijuana-...

The JS behavior regarding 1/0, etc, is the same as C: http://www.gnu.org/software/libc/manual/html_node/Infinity-a...

Most browsers support user stylesheets, either built-in (Firefox/Safari) or as an extension, which can accomplish this.

49.0.1

On Safari, both of these examples flash the underlying panel before the transition takes place. On Firefox, the transition is quite choppy. Is this just me? (I'm sure there's a simple fix, i.e. maybe one of the layers isn't getting composited the whole time...)

I think they're referring to any non-web language, e.g. if I could host and distribute C apps with the ease of the web. (Getting end-users to actually run and use a program with one click, rather than having to download a binary, run it separately, etc.)

This (somewhat insane) linter prohibits unnecessary semicolons: http://standardjs.com

A sample could fall under fair use.

That's the same thing.

TextDecoder/TextEncoder is the emerging standard way to do this.

https://developer.mozilla.org/en-US/docs/Web/API/TextDecoder

Really well done. Nice job!

In this title, 'everywhere' means 'across browsers', not 'throughout all JS execution'.

Did it say which are supported?

Not every app can load instantly. Better to have a reasonable loading screen than an ugly, flickery, reflowy startup experience.

PUT and DELETE are standardized. http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html

I'm from Des Moines (now in SF); it has really matured in the last twenty years. It's a great place to live: inexpensive, nice people, plenty of space, definitely worth overlooking the stereotypes. Weather? You got it: feet of snow in the winter, hot in the summer, perfect in the fall and spring.

Yeah, but only in the most trivial sense. Generators are a very, very poor substitute for proper yield support, just as they were when Python devs used them in Twisted.

The opinions of one group do not represent the individuals therein.

That's silly. All of the methods are side-effect-free. It'd be useless and confusing to suffix some methods and not others.

We're using their EmailJS libraries for Firefox OS, and they've worked quite well so far.

(and/or "cheap")

I've used Om for several projects and have never run into a bug in the framework.

Agreed, and kudos for writing so much, so well, about these new paradigms.

I think the name "transducers" is a little unfortunate only in that it sounds very foreign to most coders, leading the concept to potentially be ignored. Don't let the name "transducers" or the relation to Clojure scare you off; you don't have to know either thing to understand how transducers can be useful.