masterj

> I'd ballpark that it's been free climbed by 100-300 people?

If you restrict that to people who've done it in a day you're probably down to a couple dozen at most.

Successfully free climbing the freerider is a lifetime achievement even for professional climbers, often requiring up to a week on the wall. To do it in under 24 hours is the realm of the most elite climbers only.

To be able to approach it as "four hours of light exercise" as Honnold did is an incredible feat in its own right, even before the whole certain-death-for-one-mistake bit gets factored in.

I do support and these issues come up all the time with yarn:

- native packages are not well-supported by yarn yet, notably node-sass since it's so widely-used

- no private module support

> And while [sitting in an office] all day isn't exactly the worst thing, I could see issues if that turns into people getting depressed. [Office work] isn't really healthy.

> And while [bagging groceries] all day isn't exactly the worst thing, I could see issues if that turns into people getting depressed. [Menial labor] isn't really healthy.

> And while [driving an truck / bus / uber] all day isn't exactly the worst thing, I could see issues if that turns into people getting depressed. [Sitting all day] isn't really healthy.

UBI at least gives people options. If someone is happy playing WoW all day, and society doesn't really need them anyway... I see no harm in that. At least they have the option to quit playing and do something else. People doing menial labor often don't.

If you auto-format as a commit hook then all of the changes you see will be AST-based, and you can ignore the style.

While understanding the state of a project is important for potential adopters, might I suggest filing a GitHub issue in lieu of this comment as something that might actually have a positive outcome?

It's just applying a function to a tagged template literal at compile-time instead of run-time, but it doesn't change the semantics of the language. Calling it a one-off language is hyperbole. Think of it as a compiler optimization step.

You bring up a good point with the hard-coded name though. Instead of hardcoding in the pragma it should probably check the name in the require. This wouldn't be difficult to add, and the project is only two days old.

It could be very useful for docs sites, blogs, coding books. Anything where ease-of-authoring is the highest priority. You could maintain it in markdown but also inject your custom components for examples or bits of interactivity.

Guillermo is also behind Socket.IO, Cloudup, and organizes JSConf Argentina

Have you tried Nuclide? It has good remote project support since FB web engineers have to develop on remote servers.

You can read it as "pull on gear". In "free climbing" pieces of gear are slotted inside cracks and the rope is clipped to them for safety. If you grab the gear and use it because you can't climb the natural face it doesn't count as "free-ing the route". Many routes have sections where this is mandatory or very common. There might be a great moderate climb with one small stretch that is significantly harder, so people pull on their gear through that bit and enjoy the rest.

There is also great pride in being the first one to "free a route", free climbing a route where all previous parties have used gear (also called aid climbing).

Full-on aid climbing generally involves hanging a ladder from gear, stepping up on the highest rung, and placing another piece of gear and a higher ladder. This can actually be incredibly physical and incredibly mentally taxing since the gear used might be a tiny hook hanging off a dime edge, or a postage-stamp sized piton hammered into a seam.

Hope that helps!

And 4TB these days only costs ~$120 http://www.amazon.com/Seagate-SATA-3-5-Inch-Desktop-ST4000DM... though it's still a chore to manage and backup so many photos

> Not everyone has Facebook's budget or resources to upgrade every 2 months.

Even if you're FB, dedicating the engineering time to upgrading/testing/deploying 15k+ components by making a breaking change would be madness.

Anecdotally, when the React team breaks something (rare) a lot of people internally start yelling, and it never makes it into the releases. FB makes for one-hell of an integration test environment.

Why do you care about an imaginary number? FB (and many other large companies) heavily use this in production, and have to migrate their own apps. FB even goes farther and uses the master branch (well, synced every week or so). That's a far heavier endorsement than whatever side of a decimal a number falls on.

It's competitor from facebook (http://flowtype.org/) is also really fast during development as well, even for sweeping changes across big sections of the code base.

It's scalable with the right tools. If you can write a transform at the level of the AST that will make the change for you, you can do it in one commit. FB has written about this: https://medium.com/@cpojer/effective-javascript-codemods-5a6...

Not that it's a silver bullet, but it can make a lot of these cases non-issues.

In the example you used you're re-defining the class by wrapping it, not creating a global variable...

Consider it like:

  var a = 1;
  a = func(a);

Does it seem cleaner if you use the stateless functions from React 0.14? http://facebook.github.io/react/blog/2015/09/10/react-v0.14-...

  var Score = (props) => (
    <li key={props.score.initials}>
      <strong>{props.score.initials}</strong> {props.score.score}
    </li>
  );

  Score = Relay.createContainer(Score, {
    fragments: {
      score: () => Relay.QL`
        fragment on Score {
          initials,
          score,
        }
      `,
    },
  });

This is how Relay currently works

Self driving cars still require a significant amount of surface area that could better be utilized for: housing, bike transit, pedestrian areas, parks.

And though coordination by autonomous vehicles could cut down on highway congestion, speeds within the city are unlikely to match what a subway system could offer. You don't want cars rushing through your neighborhood at 60 mph, no matter if it's a machine or a human behind the wheel.

As an East Texas native who's now in California... sorry, Texas has some pretty vistas, but there's no comparison to the Sierras and California Coast.

God, I miss good Mexican food and TexMex though.

Facebook didn't abandon the virtual DOM approach with React Native, nor do they look at web as a second-class citizen. Rather React's approach could also be applied to native development, (wrapping the native stateful view hierarchy in a declarative model, which just happened to be in JavaScript) so that's what they did.

Angular is playing catch-up by adopting a similar rendering model. This will be to everyone's benefit.

Google is also pushing Polymer, but that's not really related to the other two.

I'm the one who wrote that ;) Didn't know it made it into the repo!

2048 - React

I'm in SF and nearly everyone I know uses Venmo. YMMV

I was referring to Mithril and Mercury. I work on a huge React app :)

First someone would have to build a large app with them...

> How does React know that only that sub-component needs to be re-rendered?

It doesn't. By default it will render the whole tree again. This happens in javascript and is probably much faster than you think.

However, when an app grows large enough, this can be a source of performance issues, which is why React provides ways you can inform it about work it shouldn't have to do, namely shouldComponentUpdate. If you can compare the data and determine that a particular sub-tree doesn't need to be updated you can implement a shouldComponentUpdate callback that does this. Immutable data that can be cheaply compared by checking reference equality is the preferred way of doing this.

More info on this was recently added to the docs: http://facebook.github.io/react/docs/advanced-performance.ht...

Small note: Alex and Hans did not set the speed record by freeing the Nose. They definitely aided sections.

Only 4 people have successfully free'd the Nose. The 4th happened only last November. So far it happens about once a decade. (http://www.rockandice.com/lates-news/jorg-verhoeven-free-cli...)

- Games are always good places to start. Start with something simple like tetris.

- Pick your favorite unix utility and re-build it.

> What if you chose React based on your current opinion and next year React version 2.0 (or whatever) changes the entire core...

React is heavily used in production at Facebook (~10k components), and any breaking changes are going to have an upgrade path. Facebook is essentially always running React master.