sim0n

Looks perfectly fine in FF 144.0 on Mac OS.

I would assume that lot of people just find the JSX equivalent a lot more readable and familiar (a matter of opinion, of course.)

  <div>
    <p>this is easy</p>
    {list.map((l) => <li>{l}</li>)}
  </div>

To be fair to JSX, you use regular loops, interpolation, etc without any different syntax (`{}` accepts a vanilla JS expression), you just obviously need the compiler step to de-sugar the element tags to `createElement` calls.

That's not particularly high for a large scale web application where every file is a ES module, especially so if it includes dependencies.

Nothing is "wrong" with it, the design is just something from the 90s/early 2000s.

They haven't.

One case I've come across them using it for is delivering updates for visible tweets in a timeline (e.g. like/retweet counts being mutated).

Not exactly a framework, but a React app from 2014 will still work great in 2019 and can be updated with very little pain.

Build tools wise, a simple Webpack/Babel config from 2014 would be relatively straightforward to update to the latest versions.

Soccer would be a much better sport

Very subjective. I personally think having a limited set of substitutions helps keep the game more interesting as every change can be hugely impactful to the team's tactics and the result of the game.

Why is "map an array with a function" unintuitive but "filter an array with a function" isn't?

I'm sure they do. This is pretty standard at lots of big tech companies (Airbnb, most likely Uber, etc).

there should be a repository called mathiasbynens.github.io right

Not exactly - the subdomain is the account and the path name is the repository (and the repository's `gh-pages` branch is what's returned).

(https://github.com/mathiasbynens/rel-noopener)

DOM APIs have much improved since jQuery first arrived, so while that was the case originally, it's become less true over time. It's definitely still less verbose though, for example:

  $('.my-component div').css({ background: 'yellow' })

  Array.from(document.querySelectorAll('.my-component div')).map(node => {
    node.style.background = 'yellow';
  })

The article says they will no longer allow Touch ID to trust a computer, I imagine they also won't allow Face ID.

Is Symbian OS still a thing? From Wikipedia:

Nokia terminated its support of software development and maintenance for Symbian with effect from 1 January 2014, thereafter refusing to publish new or changed Symbian applications or content in the Nokia Store and terminating its 'Symbian Signed' program for software certification. (http://www.allaboutsymbian.com/news/item/18502_New_Symbian_a...)

I personally think that the syntax is great considering it's being added to an existing language. await/async allows you to opt-in to having your code behave in a synchronous-like manner, when you want it to.

One of the best things about JS/Node is that you can wait on I/O from different sources at the same time and since the async/await syntax is just sugar over Promises, you can do things like:

  const [user, notifications, messages] = await Promise.all([
    getUser(),
    getNotifications(),
    getMessages(),
  ]);

  const user = getUser();
  const notifications = getNotifications();
  const messages = getMessages();

FWIW, you can use `Symbol.for` to reuse symbols in JS (`Symbol.for("a") === Symbol.for("a")` is true).

Does any major tech company use Dart other than Google?

You don't have to use the hottest new framework or language feature. The JavaScript you're writing now will still be supported while the language evolves and improves.

For anyone confused/concerned, the title of this thread is currently "USCIS Will Temporarily Suspend Premium Processing for All Petitions" despite only H-1Bs actually being affected. The title should probably be updated to clarify it only affects one category (H-1B).

Are you mistaking this for the ESTA application form allowing people to enter their social media handles?

The backend where I work (Airbnb) runs on Rails but most of my projects use node on the backend since they usually just expose a REST API.

Since it only cares about UI, React is obviously not opinionated about your backend/server environment unless you're trying to do server rendering (then you need something in your stack capable of executing JS).

For view/UI, yes (if you can call React a framework). I personally do not use jQuery anymore as there is not much need to deal with the DOM directly when using React and when there is, I just use vanilla JS.

Since React only deals with UI, I use it alongside a bunch of other great libraries such as Redux (for state management).

For me, once I started declaring my UI as a series of components that simply render what they are provided (the common `v = f(d)` expression), it was hard to go back to the Backbone/jQuery way of mutating things all over the place and manually updating DOM nodes to try and reflect the current app state.

You don't need either to incorporate (at least not in my experience w/ Delaware).

You are not taught how drive as part of the curriculum in England and is not offered to students by schools like it is in the US.

Definitely still called debit cards in the UK.

How could you take advantage of the leak without JavaScript?

Screenshot of what I can see: http://i.imgur.com/0F2Cjyv.png.

Sounds like she imitated the behaviour of a 14 year old on the internet pretty well.

Thats the obvious solution, though how would that affect people using Netlfix while traveling?

For example, if you're locked to the US region and watch something that is only available in the US while visiting, say, the UK — would that break any of Netflix's license agreements?